Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc8c139c0b7133488a704064c1c5b8452d8b2032612ebbe8a0bd63271b555e19

Tx prefix hash: 1d1b299c2c65ed30dc53f2200b2485b0c83218c82af13b688ecb6d047ece3d01
Tx public key: b27649451a64a9feff05d5307501c63108731b14bc7d218dd5a41cc3f239fc9c
Timestamp: 1738629566 Timestamp [UCT]: 2025-02-04 00:39:26 Age [y:d:h:m:s]: 00:288:13:29:07
Block: 1211557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204014 RingCT/type: yes/0
Extra: 01b27649451a64a9feff05d5307501c63108731b14bc7d218dd5a41cc3f239fc9c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cc707f482479f73d0d781de50a369938e297be79bc45595d27d05bcf920a7c2 0.600000000000 1698318 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": 1211567, "vin": [ { "gen": { "height": 1211557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cc707f482479f73d0d781de50a369938e297be79bc45595d27d05bcf920a7c2" } } ], "extra": [ 1, 178, 118, 73, 69, 26, 100, 169, 254, 255, 5, 213, 48, 117, 1, 198, 49, 8, 115, 27, 20, 188, 125, 33, 141, 213, 164, 28, 195, 242, 57, 252, 156, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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