Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b0607ced7a476c0aa9ecf0d29a31eb50df4bd791d2a157c0950e18072ccda49

Tx prefix hash: 81a617e2f87b3b16eadf4cea6b2cc2b455f6c84145c8a3abcf313a384e27446b
Tx public key: 3aa6bb57f1f9b79881e79ceca673653655f8233ba3c953fa6631dcf5dcc3b1fa
Timestamp: 1709033556 Timestamp [UCT]: 2024-02-27 11:32:36 Age [y:d:h:m:s]: 01:017:11:43:21
Block: 966646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273524 RingCT/type: yes/0
Extra: 013aa6bb57f1f9b79881e79ceca673653655f8233ba3c953fa6631dcf5dcc3b1fa02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac5eab77f2e67689ba36ab387da166c3fc42cb58ca7ae840779851cb7bf94c5e 0.600000000000 1426413 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": 966656, "vin": [ { "gen": { "height": 966646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac5eab77f2e67689ba36ab387da166c3fc42cb58ca7ae840779851cb7bf94c5e" } } ], "extra": [ 1, 58, 166, 187, 87, 241, 249, 183, 152, 129, 231, 156, 236, 166, 115, 101, 54, 85, 248, 35, 59, 163, 201, 83, 250, 102, 49, 220, 245, 220, 195, 177, 250, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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