Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6bceef4ae4b0c160b10cc7329657d338c3a7d064c35778e547bb0010a99800f

Tx prefix hash: 6b49beed5a3756ac246abfde3693ad112d0f2d7966ca6a79c3bdffad6f69afb4
Tx public key: 94e08bcf6521cdeb29d1ee04633dbe85626d6cd7997ec4db83ff43c4a82e731b
Timestamp: 1719044992 Timestamp [UCT]: 2024-06-22 08:29:52 Age [y:d:h:m:s]: 01:139:07:55:06
Block: 1049622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358145 RingCT/type: yes/0
Extra: 0194e08bcf6521cdeb29d1ee04633dbe85626d6cd7997ec4db83ff43c4a82e731b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b00f322ee9a09919718aacdfb8a5f67c2d8ee37ae5d8da48b2f016981318ae0c 0.600000000000 1519723 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": 1049632, "vin": [ { "gen": { "height": 1049622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b00f322ee9a09919718aacdfb8a5f67c2d8ee37ae5d8da48b2f016981318ae0c" } } ], "extra": [ 1, 148, 224, 139, 207, 101, 33, 205, 235, 41, 209, 238, 4, 99, 61, 190, 133, 98, 109, 108, 215, 153, 126, 196, 219, 131, 255, 67, 196, 168, 46, 115, 27, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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