Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf8c2b55cc1b733b2a207779f34c3b10d019ae28ab382f25d552867cf6613b92

Tx prefix hash: df9f548ff29503b9ea44f3fcfb048f4118dcb9fd5e2fcd3f31c76aa4a5851ce5
Tx public key: 1637e77063c5abc8225fa0a0a1742fdd4a4d2e891f92659078bb9b9d08a8681f
Timestamp: 1645860665 Timestamp [UCT]: 2022-02-26 07:31:05 Age [y:d:h:m:s]: 02:253:18:32:08
Block: 446754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 700731 RingCT/type: yes/0
Extra: 011637e77063c5abc8225fa0a0a1742fdd4a4d2e891f92659078bb9b9d08a8681f0211000000025eb576c5000000000000000000

1 output(s) for total of 20.310416297000 dcy

stealth address amount amount idx
00: 6daef67207d969e9de709d9a57eb42eac9c7ef820ec84b8973baf26e8591443d 20.310416297000 860709 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": 446764, "vin": [ { "gen": { "height": 446754 } } ], "vout": [ { "amount": 20310416297, "target": { "key": "6daef67207d969e9de709d9a57eb42eac9c7ef820ec84b8973baf26e8591443d" } } ], "extra": [ 1, 22, 55, 231, 112, 99, 197, 171, 200, 34, 95, 160, 160, 161, 116, 47, 221, 74, 77, 46, 137, 31, 146, 101, 144, 120, 187, 155, 157, 8, 168, 104, 31, 2, 17, 0, 0, 0, 2, 94, 181, 118, 197, 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