Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484c25d6777b9dcb4985da7fabe98ed5724e03e26163b952a6b6ad0bf56fa71a

Tx prefix hash: 297a3c91d04f62fcc04ff7d0ef3f299e5ae0f0b3200a9deb60ddfeaec085bb0f
Tx public key: 91b21f5e66e20ebef775550148851147f5d9fe01cac7b1014d95f2f549ed7f1b
Timestamp: 1735950719 Timestamp [UCT]: 2025-01-04 00:31:59 Age [y:d:h:m:s]: 00:168:15:06:26
Block: 1189667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120183 RingCT/type: yes/0
Extra: 0191b21f5e66e20ebef775550148851147f5d9fe01cac7b1014d95f2f549ed7f1b02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24ad9414477c2a052434a6858f6e7cd3bd703ee49c20fc272fa330eb5ae0e158 0.600000000000 1676178 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": 1189677, "vin": [ { "gen": { "height": 1189667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24ad9414477c2a052434a6858f6e7cd3bd703ee49c20fc272fa330eb5ae0e158" } } ], "extra": [ 1, 145, 178, 31, 94, 102, 226, 14, 190, 247, 117, 85, 1, 72, 133, 17, 71, 245, 217, 254, 1, 202, 199, 177, 1, 77, 149, 242, 245, 73, 237, 127, 27, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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