Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441fe8c322f27354a5dc69ba73427452566c2e52bf82d5318da6c69489805b71

Tx prefix hash: a934edbde5eb36f7685bbf7985b7f48e532ea9bb8ac3744fabc328e8f6e93e0c
Tx public key: f4e19cc46ec7704ea37666102a89bb221e5a33f34563089bf0dc9870f96aa557
Timestamp: 1734046087 Timestamp [UCT]: 2024-12-12 23:28:07 Age [y:d:h:m:s]: 00:336:00:30:08
Block: 1173917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237660 RingCT/type: yes/0
Extra: 01f4e19cc46ec7704ea37666102a89bb221e5a33f34563089bf0dc9870f96aa557021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96ed39e3b8cf50050a079bf7dea4c790b1431c4ae759f9dcca827644cbbf6d1e 0.600000000000 1660004 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": 1173927, "vin": [ { "gen": { "height": 1173917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96ed39e3b8cf50050a079bf7dea4c790b1431c4ae759f9dcca827644cbbf6d1e" } } ], "extra": [ 1, 244, 225, 156, 196, 110, 199, 112, 78, 163, 118, 102, 16, 42, 137, 187, 34, 30, 90, 51, 243, 69, 99, 8, 155, 240, 220, 152, 112, 249, 106, 165, 87, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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