Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49201b9fd5ecbc0a444ee3ca1ee41c4e576790e0a85f2629467850190b9bfaf9

Tx prefix hash: e66a6ce9beff4d0907f7d3e8a91ee530f8db9684a68becf6644b50e0d3acdbf7
Tx public key: 9d1334cdea385efdc07b60c4974ad3ce92fd6cf22053a91cfbbfb3d3edabc0e3
Timestamp: 1711281774 Timestamp [UCT]: 2024-03-24 12:02:54 Age [y:d:h:m:s]: 00:235:06:11:37
Block: 985298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168406 RingCT/type: yes/0
Extra: 019d1334cdea385efdc07b60c4974ad3ce92fd6cf22053a91cfbbfb3d3edabc0e30211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dbbbd79eca0b460dce3da7660af59780153ca2f5dc51c8d11e5afa12c0fb60d 0.600000000000 1445507 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": 985308, "vin": [ { "gen": { "height": 985298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dbbbd79eca0b460dce3da7660af59780153ca2f5dc51c8d11e5afa12c0fb60d" } } ], "extra": [ 1, 157, 19, 52, 205, 234, 56, 94, 253, 192, 123, 96, 196, 151, 74, 211, 206, 146, 253, 108, 242, 32, 83, 169, 28, 251, 191, 179, 211, 237, 171, 192, 227, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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