Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f31845829325f8481fd44d870669f5b33b66eecb9888888737367289aa2ed280

Tx prefix hash: 58396cf4a42f601051c70f3a2e72c6647fac896113eb0a9c5cb8f2b9a714c361
Tx public key: 84d3d55061cad13304f2bd17a71ce5acc3fd63b32844f3eacaa3882b77f49579
Timestamp: 1627532241 Timestamp [UCT]: 2021-07-29 04:17:21 Age [y:d:h:m:s]: 03:119:15:26:42
Block: 302962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 857944 RingCT/type: yes/0
Extra: 0184d3d55061cad13304f2bd17a71ce5acc3fd63b32844f3eacaa3882b77f4957902110000002cb6cb3507000000000000000000

1 output(s) for total of 60.836134956000 dcy

stealth address amount amount idx
00: 79c3ed7828810a7a90b9fb91928f7615c05d703d1dfb0a80b36d8d61228bac51 60.836134956000 632441 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": 302972, "vin": [ { "gen": { "height": 302962 } } ], "vout": [ { "amount": 60836134956, "target": { "key": "79c3ed7828810a7a90b9fb91928f7615c05d703d1dfb0a80b36d8d61228bac51" } } ], "extra": [ 1, 132, 211, 213, 80, 97, 202, 209, 51, 4, 242, 189, 23, 167, 28, 229, 172, 195, 253, 99, 179, 40, 68, 243, 234, 202, 163, 136, 43, 119, 244, 149, 121, 2, 17, 0, 0, 0, 44, 182, 203, 53, 7, 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