Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 886ac3115e96414b612eb7659c8ff80c4ef9771a3db9c4b5ae9115c14172d90a

Tx prefix hash: 4d2060ac5ba68117929f271901885957055eb353806a063d11febe33b0568e79
Tx public key: e5e1a0ed6b79bc1b2983927d81a0015fbeecaf9e730154a876b7acd1422ef825
Timestamp: 1729572204 Timestamp [UCT]: 2024-10-22 04:43:24 Age [y:d:h:m:s]: 00:033:02:40:18
Block: 1136872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23661 RingCT/type: yes/0
Extra: 01e5e1a0ed6b79bc1b2983927d81a0015fbeecaf9e730154a876b7acd1422ef8250211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aac9503ed8fe54b709cc2d8ea7b52c9b0dd33eaf4500065fbe1031d4b336b8d5 0.600000000000 1620261 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": 1136882, "vin": [ { "gen": { "height": 1136872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aac9503ed8fe54b709cc2d8ea7b52c9b0dd33eaf4500065fbe1031d4b336b8d5" } } ], "extra": [ 1, 229, 225, 160, 237, 107, 121, 188, 27, 41, 131, 146, 125, 129, 160, 1, 95, 190, 236, 175, 158, 115, 1, 84, 168, 118, 183, 172, 209, 66, 46, 248, 37, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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