Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cecb83a3ab2d7fd6b12dd1217dd3e1a6b164da463ce3814979a7f9930cbc0b4f

Tx prefix hash: e84883319448e9aac4e1a0ada6f8cc517a434be193bdf0b76f32bfc55f41a825
Tx public key: b06c76692345fb72fcce1093c8acc9726638eda1b524d8261ad075a624476d37
Timestamp: 1646642694 Timestamp [UCT]: 2022-03-07 08:44:54 Age [y:d:h:m:s]: 03:031:08:00:29
Block: 453149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 802523 RingCT/type: yes/0
Extra: 01b06c76692345fb72fcce1093c8acc9726638eda1b524d8261ad075a624476d370211000000034a0f5013000000000000000000

1 output(s) for total of 19.343253617000 dcy

stealth address amount amount idx
00: 39f1ee4ff9e34e981c8317cd0992b43d4db0079b82d538df7c971d21bf51eae6 19.343253617000 868572 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": 453159, "vin": [ { "gen": { "height": 453149 } } ], "vout": [ { "amount": 19343253617, "target": { "key": "39f1ee4ff9e34e981c8317cd0992b43d4db0079b82d538df7c971d21bf51eae6" } } ], "extra": [ 1, 176, 108, 118, 105, 35, 69, 251, 114, 252, 206, 16, 147, 200, 172, 201, 114, 102, 56, 237, 161, 181, 36, 216, 38, 26, 208, 117, 166, 36, 71, 109, 55, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 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