Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9278a4cf3baec71cd6bd1dc77136be5cf2a6cef87dd4a091f5aa9cfc990e674

Tx prefix hash: ef0332227cf9b102c05e72db502514601e05664407700763a7feaa6e92e3e064
Tx public key: 015a9dff17a21fea1fc7c6709ed5357e4d75fc1d8bde950d6a403acf82bc79f2
Timestamp: 1756175112 Timestamp [UCT]: 2025-08-26 02:25:12 Age [y:d:h:m:s]: 00:120:06:08:10
Block: 1354542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85916 RingCT/type: yes/0
Extra: 01015a9dff17a21fea1fc7c6709ed5357e4d75fc1d8bde950d6a403acf82bc79f20211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00c8dd47166c2128ca730d5b6c9387d1ce6523dc996db285caaf36ca7402fee7 0.600000000000 1842531 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": 1354552, "vin": [ { "gen": { "height": 1354542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00c8dd47166c2128ca730d5b6c9387d1ce6523dc996db285caaf36ca7402fee7" } } ], "extra": [ 1, 1, 90, 157, 255, 23, 162, 31, 234, 31, 199, 198, 112, 158, 213, 53, 126, 77, 117, 252, 29, 139, 222, 149, 13, 106, 64, 58, 207, 130, 188, 121, 242, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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