Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae2ab574280ac508109db0255b04751b11031eedd70985ee61597035fa8dcefd

Tx prefix hash: 3f34ece89173c2076b3f07adfcbc1980b52a2c747602454e726da6d9a13ada9a
Tx public key: c129bf99c123ce4f5b1a9d67c8fa1e7519adf0bb076e2dc4a19685a4d7fad76b
Timestamp: 1706512433 Timestamp [UCT]: 2024-01-29 07:13:53 Age [y:d:h:m:s]: 01:051:19:12:11
Block: 945714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298112 RingCT/type: yes/0
Extra: 01c129bf99c123ce4f5b1a9d67c8fa1e7519adf0bb076e2dc4a19685a4d7fad76b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6223bfd9144fcc4b3091f2f673f2ee149bcd744914ab8d2c69bec1d2cbc3ff63 0.600000000000 1404032 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": 945724, "vin": [ { "gen": { "height": 945714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6223bfd9144fcc4b3091f2f673f2ee149bcd744914ab8d2c69bec1d2cbc3ff63" } } ], "extra": [ 1, 193, 41, 191, 153, 193, 35, 206, 79, 91, 26, 157, 103, 200, 250, 30, 117, 25, 173, 240, 187, 7, 110, 45, 196, 161, 150, 133, 164, 215, 250, 215, 107, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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