Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37909cec67752214cf3b03236b45b6cfd727f108d54c53e1a49d6b015220f840

Tx prefix hash: f417839c0a0f0761793309da6ae2306f6c949f2014f361ef7e486e6d1aa164e6
Tx public key: d69f1fbbbe8bde8a98e909062cb4a694af00163a523edf858c5e6912caa6d9f4
Timestamp: 1582771734 Timestamp [UCT]: 2020-02-27 02:48:54 Age [y:d:h:m:s]: 04:306:08:47:45
Block: 72473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112513 RingCT/type: yes/0
Extra: 01d69f1fbbbe8bde8a98e909062cb4a694af00163a523edf858c5e6912caa6d9f40211000000084ac5aa02000000000000000000

1 output(s) for total of 353.075567706000 dcy

stealth address amount amount idx
00: cb0cff5789c39629ae7def46d16cd9c5489c2aae800508f985960edb981100f8 353.075567706000 133935 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": 72483, "vin": [ { "gen": { "height": 72473 } } ], "vout": [ { "amount": 353075567706, "target": { "key": "cb0cff5789c39629ae7def46d16cd9c5489c2aae800508f985960edb981100f8" } } ], "extra": [ 1, 214, 159, 31, 187, 190, 139, 222, 138, 152, 233, 9, 6, 44, 180, 166, 148, 175, 0, 22, 58, 82, 62, 223, 133, 140, 94, 105, 18, 202, 166, 217, 244, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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