Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250fe4723f5a05f815235062fdf040199dab8edb671fae024e58fbda74f19136

Tx prefix hash: f81f4cfb01c0fd4d88a147fe801fc0188417c0970663f114101009a659e27cb3
Tx public key: dc1443d251b4bc99b5fe99e9aca79ebcb68fffce69347a16c7ba2f2b4091f7a1
Timestamp: 1727326471 Timestamp [UCT]: 2024-09-26 04:54:31 Age [y:d:h:m:s]: 00:202:12:44:43
Block: 1118296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144563 RingCT/type: yes/0
Extra: 01dc1443d251b4bc99b5fe99e9aca79ebcb68fffce69347a16c7ba2f2b4091f7a1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f752550fa13a1654e6dce138151b7b0c8c5e97c956b1c2667f492c99f7ba8349 0.600000000000 1599439 of 15

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": 1118306, "vin": [ { "gen": { "height": 1118296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f752550fa13a1654e6dce138151b7b0c8c5e97c956b1c2667f492c99f7ba8349" } } ], "extra": [ 1, 220, 20, 67, 210, 81, 180, 188, 153, 181, 254, 153, 233, 172, 167, 158, 188, 182, 143, 255, 206, 105, 52, 122, 22, 199, 186, 47, 43, 64, 145, 247, 161, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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