Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72f09d15378268fbbedfac7efc52470d19f8fb2417013e18802d47ae1b64128

Tx prefix hash: 06c4fd2a15f4c41e06002d7a4dd8da1e5d88b19ad65cdaec5d19b2854857be6f
Tx public key: 858b5cebfc381ab7ace21dc5e46aaa95a71518c8d2eddeb08d2b22404e98e5dd
Timestamp: 1706286923 Timestamp [UCT]: 2024-01-26 16:35:23 Age [y:d:h:m:s]: 00:292:17:26:50
Block: 943840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209614 RingCT/type: yes/0
Extra: 01858b5cebfc381ab7ace21dc5e46aaa95a71518c8d2eddeb08d2b22404e98e5dd02110000000181d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2d65cab65e9b33e99425855f79dd869b49038f37fb275da190311e74eee3bd3 0.600000000000 1402066 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": 943850, "vin": [ { "gen": { "height": 943840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2d65cab65e9b33e99425855f79dd869b49038f37fb275da190311e74eee3bd3" } } ], "extra": [ 1, 133, 139, 92, 235, 252, 56, 26, 183, 172, 226, 29, 197, 228, 106, 170, 149, 167, 21, 24, 200, 210, 237, 222, 176, 141, 43, 34, 64, 78, 152, 229, 221, 2, 17, 0, 0, 0, 1, 129, 215, 29, 85, 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