Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f053d0f3be670177fb0be447fdccc0c99f94ed2daf9213cda7fc4907c03d7119

Tx prefix hash: bb508ee8b865e9ddd9c6bb2d64ea63176a4ed58638506a58755888ab5b3bee87
Tx public key: 689a20e90fe2be87be2686db08415ee311d23db7d591327a5c26c3c37d810731
Timestamp: 1639158581 Timestamp [UCT]: 2021-12-10 17:49:41 Age [y:d:h:m:s]: 03:329:13:48:31
Block: 392651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1011992 RingCT/type: yes/0
Extra: 01689a20e90fe2be87be2686db08415ee311d23db7d591327a5c26c3c37d81073102110000000137cb3088000000000000000000

1 output(s) for total of 30.689131776000 dcy

stealth address amount amount idx
00: 5c2a5c126205fc30d0ca8a2e0d2671a6a3f8bb762ff6a15216102f35fec1b1eb 30.689131776000 789600 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": 392661, "vin": [ { "gen": { "height": 392651 } } ], "vout": [ { "amount": 30689131776, "target": { "key": "5c2a5c126205fc30d0ca8a2e0d2671a6a3f8bb762ff6a15216102f35fec1b1eb" } } ], "extra": [ 1, 104, 154, 32, 233, 15, 226, 190, 135, 190, 38, 134, 219, 8, 65, 94, 227, 17, 210, 61, 183, 213, 145, 50, 122, 92, 38, 195, 195, 125, 129, 7, 49, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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