Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9936d6ee71ff43592d1cb60b71240e1bb82bd75a33423ce4489aa178ef49f4f

Tx prefix hash: 748fa01feef6f3e7607082e8fcb31e62964de9220e446b4d9bf484d138753374
Tx public key: c3f5a552d7a67d2b801594a8158d8e621f77f96d16cefb38c57724e889da8959
Timestamp: 1576281844 Timestamp [UCT]: 2019-12-14 00:04:04 Age [y:d:h:m:s]: 05:017:01:04:15
Block: 26565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158814 RingCT/type: yes/0
Extra: 01c3f5a552d7a67d2b801594a8158d8e621f77f96d16cefb38c57724e889da895902110000001cad433a0b000000000000000000

1 output(s) for total of 501.164147473000 dcy

stealth address amount amount idx
00: bcbcd8541f61d3965e1f4cc1324fc3db11da1edc1faad22b4d4bdf2325f4efa8 501.164147473000 44022 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": 26575, "vin": [ { "gen": { "height": 26565 } } ], "vout": [ { "amount": 501164147473, "target": { "key": "bcbcd8541f61d3965e1f4cc1324fc3db11da1edc1faad22b4d4bdf2325f4efa8" } } ], "extra": [ 1, 195, 245, 165, 82, 215, 166, 125, 43, 128, 21, 148, 168, 21, 141, 142, 98, 31, 119, 249, 109, 22, 206, 251, 56, 197, 119, 36, 232, 137, 218, 137, 89, 2, 17, 0, 0, 0, 28, 173, 67, 58, 11, 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