Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b88bf6eebe90ea64765c17717de80acb2135593451ce26d5c864721cefe433

Tx prefix hash: 144f004db7dd1bd3a0529b497fd825c839482dc5feace368b4a47fab3b4d2ff3
Tx public key: 5e4f863372d796677be227268a4a3c0ca1e528b2b0826f994cb0f965c8eaeedc
Timestamp: 1716327257 Timestamp [UCT]: 2024-05-21 21:34:17 Age [y:d:h:m:s]: 00:187:09:00:49
Block: 1027107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134117 RingCT/type: yes/0
Extra: 015e4f863372d796677be227268a4a3c0ca1e528b2b0826f994cb0f965c8eaeedc0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e04edd3513bcbee16a32f154318e72ca76d6f73182ccd1f31aa766c087ca8a 0.600000000000 1494558 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": 1027117, "vin": [ { "gen": { "height": 1027107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e04edd3513bcbee16a32f154318e72ca76d6f73182ccd1f31aa766c087ca8a" } } ], "extra": [ 1, 94, 79, 134, 51, 114, 215, 150, 103, 123, 226, 39, 38, 138, 74, 60, 12, 161, 229, 40, 178, 176, 130, 111, 153, 76, 176, 249, 101, 200, 234, 238, 220, 2, 17, 0, 0, 0, 2, 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