Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48563d6e3b6647aa8ec3e0774498fd0d429fd8a23852e3120de6e4a51cd76c5e

Tx prefix hash: f946ba71bead9885173df0ea113a7690b72d2a65c85f6a094adf23388e5f6875
Tx public key: f4e13326ad823e4409ee8a9557305e340a4f1d20dcf54c56fe326203dee93280
Timestamp: 1648514515 Timestamp [UCT]: 2022-03-29 00:41:55 Age [y:d:h:m:s]: 02:237:17:49:21
Block: 468564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689433 RingCT/type: yes/0
Extra: 01f4e13326ad823e4409ee8a9557305e340a4f1d20dcf54c56fe326203dee932800211000000044a0f5013000000000000000000

1 output(s) for total of 17.197020517000 dcy

stealth address amount amount idx
00: 4abb45b4c376cf8b2de45e02d1757abadaf990ac1b419f0f51638a93950ca4f7 17.197020517000 887304 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": 468574, "vin": [ { "gen": { "height": 468564 } } ], "vout": [ { "amount": 17197020517, "target": { "key": "4abb45b4c376cf8b2de45e02d1757abadaf990ac1b419f0f51638a93950ca4f7" } } ], "extra": [ 1, 244, 225, 51, 38, 173, 130, 62, 68, 9, 238, 138, 149, 87, 48, 94, 52, 10, 79, 29, 32, 220, 245, 76, 86, 254, 50, 98, 3, 222, 233, 50, 128, 2, 17, 0, 0, 0, 4, 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