Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfd8f1b835c0ba2ce0fa003b890f1e12b0c76d59350ecdf0bff409ffd6e74a0f

Tx prefix hash: 628c59948f8e5283d96714db38ee2a8dd6747f8de887753c61765234c069a0df
Tx public key: 52c261e843f55551f06a1c81a8a7567dd8bdd1daf64981fc053d05ead58968ec
Timestamp: 1582092146 Timestamp [UCT]: 2020-02-19 06:02:26 Age [y:d:h:m:s]: 04:356:04:16:54
Block: 67837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146887 RingCT/type: yes/0
Extra: 0152c261e843f55551f06a1c81a8a7567dd8bdd1daf64981fc053d05ead58968ec0211000000094943cd9f000000000000000000

1 output(s) for total of 365.787335806000 dcy

stealth address amount amount idx
00: 31a5e9d7f4d4b44d3a0c11a96d6e20af0844a03768d2937b0a309e4427342e9b 365.787335806000 125001 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": 67847, "vin": [ { "gen": { "height": 67837 } } ], "vout": [ { "amount": 365787335806, "target": { "key": "31a5e9d7f4d4b44d3a0c11a96d6e20af0844a03768d2937b0a309e4427342e9b" } } ], "extra": [ 1, 82, 194, 97, 232, 67, 245, 85, 81, 240, 106, 28, 129, 168, 167, 86, 125, 216, 189, 209, 218, 246, 73, 129, 252, 5, 61, 5, 234, 213, 137, 104, 236, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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