Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f633d6fb51e85886fecb19b0dd9042db31f527cdc3839e0b6c69b0c58ebf97a

Tx prefix hash: 49f0a56f19f749da4b6f677b34f586b4f9279d72bdeba79efad67aa88152b960
Tx public key: 46994e1c738de1f76ddf046c5baf76f0f2760f2a14431f5f16eaeeed88c729b0
Timestamp: 1577122163 Timestamp [UCT]: 2019-12-23 17:29:23 Age [y:d:h:m:s]: 05:072:12:17:04
Block: 30044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201703 RingCT/type: yes/0
Extra: 0146994e1c738de1f76ddf046c5baf76f0f2760f2a14431f5f16eaeeed88c729b00211000000254ac5aa02000000000000000000

1 output(s) for total of 488.036853399000 dcy

stealth address amount amount idx
00: 962f3f83bbdf4ec10fb0230f1d7a608fb2161a27a1c9e983242df79ea06b116b 488.036853399000 49596 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": 30054, "vin": [ { "gen": { "height": 30044 } } ], "vout": [ { "amount": 488036853399, "target": { "key": "962f3f83bbdf4ec10fb0230f1d7a608fb2161a27a1c9e983242df79ea06b116b" } } ], "extra": [ 1, 70, 153, 78, 28, 115, 141, 225, 247, 109, 223, 4, 108, 91, 175, 118, 240, 242, 118, 15, 42, 20, 67, 31, 95, 22, 234, 238, 237, 136, 199, 41, 176, 2, 17, 0, 0, 0, 37, 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