Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f91c4f987518580e8ba046c5446d32628fd16d6624e2b01da3663213d3f45a73

Tx prefix hash: 257692fb26a1da474294baff1070ea2833c132fe0503756810c767c30732a1e7
Tx public key: b4c640a5645de86ae08513fd9ca50d715eb17cfdf73aa7a2010d3523aa98a9b8
Timestamp: 1714352276 Timestamp [UCT]: 2024-04-29 00:57:56 Age [y:d:h:m:s]: 01:005:08:12:22
Block: 1010726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264753 RingCT/type: yes/0
Extra: 01b4c640a5645de86ae08513fd9ca50d715eb17cfdf73aa7a2010d3523aa98a9b80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 706d9f49ae8fd6e94caff094ed149ee768da71b46c0a1e701232c0fe5614e425 0.600000000000 1472764 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": 1010736, "vin": [ { "gen": { "height": 1010726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "706d9f49ae8fd6e94caff094ed149ee768da71b46c0a1e701232c0fe5614e425" } } ], "extra": [ 1, 180, 198, 64, 165, 100, 93, 232, 106, 224, 133, 19, 253, 156, 165, 13, 113, 94, 177, 124, 253, 247, 58, 167, 162, 1, 13, 53, 35, 170, 152, 169, 184, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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