Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8460152c988aa111f0ffb5a410f522634c37027567ea77c41c7ee566c3e0df22

Tx prefix hash: f74c97f29ea39374347f62807e68335cc14f1f966c03b92947620d82e0df1a43
Tx public key: e1f119f51ef2db8947f554327b6a0b61710e994912ecf7ab7795f5f76e6d5257
Timestamp: 1725134264 Timestamp [UCT]: 2024-08-31 19:57:44 Age [y:d:h:m:s]: 00:215:06:10:13
Block: 1100120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153687 RingCT/type: yes/0
Extra: 01e1f119f51ef2db8947f554327b6a0b61710e994912ecf7ab7795f5f76e6d5257021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70250ad0e3c87c904c2f4002b4ef1096a019d8ae725d1204a241cb95f3a177fb 0.600000000000 1576093 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1100130, "vin": [ { "gen": { "height": 1100120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70250ad0e3c87c904c2f4002b4ef1096a019d8ae725d1204a241cb95f3a177fb" } } ], "extra": [ 1, 225, 241, 25, 245, 30, 242, 219, 137, 71, 245, 84, 50, 123, 106, 11, 97, 113, 14, 153, 73, 18, 236, 247, 171, 119, 149, 245, 247, 110, 109, 82, 87, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8