Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec561dc88b168315a57be1f23cd4ce6a4d4f30b2ae9b220ceedbc290c49e2bd5

Tx prefix hash: 5f6b6462d56425913c66486aeb2b431b53686054c238e03133e2f222edc86051
Tx public key: 34de17250d98952b9c0f335ebd6a1c3ec03edc2f442264a7ea76a01124b014cb
Timestamp: 1709171831 Timestamp [UCT]: 2024-02-29 01:57:11 Age [y:d:h:m:s]: 01:054:18:48:20
Block: 967786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300172 RingCT/type: yes/0
Extra: 0134de17250d98952b9c0f335ebd6a1c3ec03edc2f442264a7ea76a01124b014cb02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 130ec78713e6acd12c607bd70075d413db5b9b6e8d8ce2a344ae441ed743dd56 0.600000000000 1427571 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": 967796, "vin": [ { "gen": { "height": 967786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "130ec78713e6acd12c607bd70075d413db5b9b6e8d8ce2a344ae441ed743dd56" } } ], "extra": [ 1, 52, 222, 23, 37, 13, 152, 149, 43, 156, 15, 51, 94, 189, 106, 28, 62, 192, 62, 220, 47, 68, 34, 100, 167, 234, 118, 160, 17, 36, 176, 20, 203, 2, 17, 0, 0, 0, 10, 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