Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c627730f1480e67db06e91d57b77cf3ff4621a07971d44b47ba37c4f9a4ae2ca

Tx prefix hash: ec558d9af4d99e508e26a2468a13558cb743a588170a12e8988860e242feeea5
Tx public key: 86b2c09d4a74ebe5560d150e0cc916145ca3ad02f4da7f10a29a7a17b613b01a
Timestamp: 1711568991 Timestamp [UCT]: 2024-03-27 19:49:51 Age [y:d:h:m:s]: 00:334:16:47:09
Block: 987676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239261 RingCT/type: yes/0
Extra: 0186b2c09d4a74ebe5560d150e0cc916145ca3ad02f4da7f10a29a7a17b613b01a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4af4150b40589f590bb3cce93836cd7e41f8a50f0fd97f6df44e43fe662067ec 0.600000000000 1447931 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": 987686, "vin": [ { "gen": { "height": 987676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4af4150b40589f590bb3cce93836cd7e41f8a50f0fd97f6df44e43fe662067ec" } } ], "extra": [ 1, 134, 178, 192, 157, 74, 116, 235, 229, 86, 13, 21, 14, 12, 201, 22, 20, 92, 163, 173, 2, 244, 218, 127, 16, 162, 154, 122, 23, 182, 19, 176, 26, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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