Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49d94bbb146c1070dd20e6c108e3cfd4399e717ff39271978a851263b31e5519

Tx prefix hash: a7e9701837c5fe7252231b2d7bb48fe65bac81bd1d5c343d50fd7924f2bc9d71
Tx public key: 0f3b4072afe1b8049252a340dde33c6407b8b8f04f3923bab37eb07f367e74a5
Timestamp: 1580702812 Timestamp [UCT]: 2020-02-03 04:06:52 Age [y:d:h:m:s]: 05:039:03:28:16
Block: 57703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179834 RingCT/type: yes/0
Extra: 010f3b4072afe1b8049252a340dde33c6407b8b8f04f3923bab37eb07f367e74a5021100000001391a8d0e000000000000000000

1 output(s) for total of 395.190803037000 dcy

stealth address amount amount idx
00: 3c64109f4ae87583defcc5e751ac36a97c14ad879d7ff4b371d2c2c252435547 395.190803037000 106642 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": 57713, "vin": [ { "gen": { "height": 57703 } } ], "vout": [ { "amount": 395190803037, "target": { "key": "3c64109f4ae87583defcc5e751ac36a97c14ad879d7ff4b371d2c2c252435547" } } ], "extra": [ 1, 15, 59, 64, 114, 175, 225, 184, 4, 146, 82, 163, 64, 221, 227, 60, 100, 7, 184, 184, 240, 79, 57, 35, 186, 179, 126, 176, 127, 54, 126, 116, 165, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 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