Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ef083e54d916a53b6bf83e3ce56f54d6eea9629fd1f61c1fdeaba13464b6aa0

Tx prefix hash: cd60f0a5745b7d500c89dad6e34d721f3390867ddc11429b6cfc5d27049b85e6
Tx public key: 5cb63497a9117d88910eedee49d8f846bd0144d37fd3001ef18b304955fbe289
Timestamp: 1583452668 Timestamp [UCT]: 2020-03-05 23:57:48 Age [y:d:h:m:s]: 04:339:17:55:16
Block: 77072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137165 RingCT/type: yes/0
Extra: 015cb63497a9117d88910eedee49d8f846bd0144d37fd3001ef18b304955fbe28902110000000b4ac5aa02000000000000000000

1 output(s) for total of 340.901776270000 dcy

stealth address amount amount idx
00: 7530b65dd20ee6283a3d4e4a59eb9fec968a3a8dc200e3d630bc6be1aeceb567 340.901776270000 141908 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": 77082, "vin": [ { "gen": { "height": 77072 } } ], "vout": [ { "amount": 340901776270, "target": { "key": "7530b65dd20ee6283a3d4e4a59eb9fec968a3a8dc200e3d630bc6be1aeceb567" } } ], "extra": [ 1, 92, 182, 52, 151, 169, 17, 125, 136, 145, 14, 237, 238, 73, 216, 248, 70, 189, 1, 68, 211, 127, 211, 0, 30, 241, 139, 48, 73, 85, 251, 226, 137, 2, 17, 0, 0, 0, 11, 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