Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 321d5bd5dc00ecf628b523a38268397c9ab915678f4ce82fa343b9d82138f72c

Tx prefix hash: 5a98105099ca9074d1f45d239e8f5c4bfc22d1762afcf923da0f92737668f2cc
Tx public key: c2cb3a0c25bf6f4692ea0b2e6538f4a336c88f41e759ae9e6e328d0e0030b41f
Timestamp: 1718548395 Timestamp [UCT]: 2024-06-16 14:33:15 Age [y:d:h:m:s]: 00:221:13:03:33
Block: 1045540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158472 RingCT/type: yes/0
Extra: 01c2cb3a0c25bf6f4692ea0b2e6538f4a336c88f41e759ae9e6e328d0e0030b41f0211000000058fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c17290ee70daa0a5325dad999340d813c752af9ab7935f5fe778920708bcadc6 0.600000000000 1515139 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": 1045550, "vin": [ { "gen": { "height": 1045540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c17290ee70daa0a5325dad999340d813c752af9ab7935f5fe778920708bcadc6" } } ], "extra": [ 1, 194, 203, 58, 12, 37, 191, 111, 70, 146, 234, 11, 46, 101, 56, 244, 163, 54, 200, 143, 65, 231, 89, 174, 158, 110, 50, 141, 14, 0, 48, 180, 31, 2, 17, 0, 0, 0, 5, 143, 218, 155, 45, 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