Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4ba3e52c3f3e3c2b57d676d3c8f255f8c6c907f78cec73af0b50809d12ad5b7

Tx prefix hash: a0158bb13411dda294f313e92479594ce09f00a7063f1838eeee95c47cf72776
Tx public key: 331768b90ef066b44588adc9d64d03d9e5f1ecfec8bf08a49115ef3c3f552f38
Timestamp: 1588737188 Timestamp [UCT]: 2020-05-06 03:53:08 Age [y:d:h:m:s]: 04:208:12:38:53
Block: 99102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1065291 RingCT/type: yes/0
Extra: 01331768b90ef066b44588adc9d64d03d9e5f1ecfec8bf08a49115ef3c3f552f3802110000000439be35fb000000000000000000

1 output(s) for total of 288.160665205000 dcy

stealth address amount amount idx
00: 333d4e854c3c61af03f6c2039af58314f4229074ee1ec1cb3ebe985cd93c6a35 288.160665205000 174948 of 0

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": 99112, "vin": [ { "gen": { "height": 99102 } } ], "vout": [ { "amount": 288160665205, "target": { "key": "333d4e854c3c61af03f6c2039af58314f4229074ee1ec1cb3ebe985cd93c6a35" } } ], "extra": [ 1, 51, 23, 104, 185, 14, 240, 102, 180, 69, 136, 173, 201, 214, 77, 3, 217, 229, 241, 236, 254, 200, 191, 8, 164, 145, 21, 239, 60, 63, 85, 47, 56, 2, 17, 0, 0, 0, 4, 57, 190, 53, 251, 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