Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2591967a766f7998c92f3383f072551da90640a94370fd5f9572e8ae759d86d

Tx prefix hash: 4945747e7e6811ece156f18263f838652379a77c8f24af1dd873c90621eb61cd
Tx public key: 79c5c3ae9ec4cc04a0df0c460a46b991ec6ae7ec42d65f3bfbee1703ad6cbe89
Timestamp: 1723805333 Timestamp [UCT]: 2024-08-16 10:48:53 Age [y:d:h:m:s]: 01:084:13:50:45
Block: 1089106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318901 RingCT/type: yes/0
Extra: 0179c5c3ae9ec4cc04a0df0c460a46b991ec6ae7ec42d65f3bfbee1703ad6cbe8902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d180ce120d7af8dd4514dd828ea6d120a7eb4653639d7e7c8c9b5106e768ac50 0.600000000000 1563725 of 15

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": 1089116, "vin": [ { "gen": { "height": 1089106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d180ce120d7af8dd4514dd828ea6d120a7eb4653639d7e7c8c9b5106e768ac50" } } ], "extra": [ 1, 121, 197, 195, 174, 158, 196, 204, 4, 160, 223, 12, 70, 10, 70, 185, 145, 236, 106, 231, 236, 66, 214, 95, 59, 251, 238, 23, 3, 173, 108, 190, 137, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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