Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b7a676019fff46ddf32f691f24634dc2d6df392540a65d12b240fc23d3c97e5

Tx prefix hash: ff8dd309d8b70c2b752dcc5808374aa6a9a5380a5e3c69aa00aa3f934e5aee82
Tx public key: 85ee818b5ef81a1adc93c1bca2082e2cf7c55a3d311279aacce70b6c5d0bcc9b
Timestamp: 1748822817 Timestamp [UCT]: 2025-06-02 00:06:57 Age [y:d:h:m:s]: 00:172:09:28:53
Block: 1295973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120883 RingCT/type: yes/0
Extra: 0185ee818b5ef81a1adc93c1bca2082e2cf7c55a3d311279aacce70b6c5d0bcc9b021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06751ca82e090517e1afaa58a15f8a0cf02c676fdb5f40355466e547b3174ecb 0.600000000000 1783480 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": 1295983, "vin": [ { "gen": { "height": 1295973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06751ca82e090517e1afaa58a15f8a0cf02c676fdb5f40355466e547b3174ecb" } } ], "extra": [ 1, 133, 238, 129, 139, 94, 248, 26, 26, 220, 147, 193, 188, 162, 8, 46, 44, 247, 197, 90, 61, 49, 18, 121, 170, 204, 231, 11, 108, 93, 11, 204, 155, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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