Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f575afe56af0fc98d22029d4d66fff501851b8d5e376d966dcdd9fd75f643690

Tx prefix hash: 584752606b494e7e36a3305a05e756007b1e31eafc03639ca37e6a271e802946
Tx public key: bb5a3db58f637a0c6d4a00534cb70373c32a2d953973c4226738723d0db6767d
Timestamp: 1703220179 Timestamp [UCT]: 2023-12-22 04:42:59 Age [y:d:h:m:s]: 01:098:03:41:27
Block: 918439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331272 RingCT/type: yes/0
Extra: 01bb5a3db58f637a0c6d4a00534cb70373c32a2d953973c4226738723d0db6767d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e97ca72e785b0331debe0583641b98d4c60765d8b83edb5a47510c69902c0de 0.600000000000 1376083 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": 918449, "vin": [ { "gen": { "height": 918439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e97ca72e785b0331debe0583641b98d4c60765d8b83edb5a47510c69902c0de" } } ], "extra": [ 1, 187, 90, 61, 181, 143, 99, 122, 12, 109, 74, 0, 83, 76, 183, 3, 115, 195, 42, 45, 149, 57, 115, 196, 34, 103, 56, 114, 61, 13, 182, 118, 125, 2, 17, 0, 0, 0, 1, 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