Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 786d1e1655b7ba135edec2520c2a5c184ae477bc858f87a9a30bf61463169988

Tx prefix hash: 27034a28aabe5184130c1cb57b7de342f7c78f86b3299ab7bfe1b194770307cf
Tx public key: 67f2ded0034ea40c1373aeed2d2528442f3991e8d101b8d3c9e4456e278e8d89
Timestamp: 1736959864 Timestamp [UCT]: 2025-01-15 16:51:04 Age [y:d:h:m:s]: 00:154:00:21:40
Block: 1198003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109790 RingCT/type: yes/0
Extra: 0167f2ded0034ea40c1373aeed2d2528442f3991e8d101b8d3c9e4456e278e8d89021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ace2c5499c0e78697cb66c27dd88e5d03f934e00a333fcb7ed0c326c4b191d3d 0.600000000000 1684620 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": 1198013, "vin": [ { "gen": { "height": 1198003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ace2c5499c0e78697cb66c27dd88e5d03f934e00a333fcb7ed0c326c4b191d3d" } } ], "extra": [ 1, 103, 242, 222, 208, 3, 78, 164, 12, 19, 115, 174, 237, 45, 37, 40, 68, 47, 57, 145, 232, 209, 1, 184, 211, 201, 228, 69, 110, 39, 142, 141, 137, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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