Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a14bfbb4c86f50714f222adb69bd2c29103bd600d6eaa62822ac552f605560a

Tx prefix hash: 433b8e3ed59f4bbfdf9fbd121a820c3a59dd29faf4d2d7ab9592d293085683a4
Tx public key: 2e5c43c279af43c5a3fffe7e2f952a652be7f8fc86ab015d018d9cedfb4da164
Timestamp: 1617602010 Timestamp [UCT]: 2021-04-05 05:53:30 Age [y:d:h:m:s]: 04:040:22:10:22
Block: 233535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1049666 RingCT/type: yes/0
Extra: 012e5c43c279af43c5a3fffe7e2f952a652be7f8fc86ab015d018d9cedfb4da16402110000001f3a645b90000000000000000000

1 output(s) for total of 103.326009749000 dcy

stealth address amount amount idx
00: 0a24fbf802cb5e7ba2eb5fb25c47c2579e6fd12d28ba26afadbf2f13aef1b9e4 103.326009749000 484969 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": 233545, "vin": [ { "gen": { "height": 233535 } } ], "vout": [ { "amount": 103326009749, "target": { "key": "0a24fbf802cb5e7ba2eb5fb25c47c2579e6fd12d28ba26afadbf2f13aef1b9e4" } } ], "extra": [ 1, 46, 92, 67, 194, 121, 175, 67, 197, 163, 255, 254, 126, 47, 149, 42, 101, 43, 231, 248, 252, 134, 171, 1, 93, 1, 141, 156, 237, 251, 77, 161, 100, 2, 17, 0, 0, 0, 31, 58, 100, 91, 144, 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