Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd80431844bc3563a0fa4f297582ccfa2d951789da881c4b66401f3b4eb66a0

Tx prefix hash: 610ab9004edf7e320c034e387dc227094a94479741fa6a099a307ad9eb3550b1
Tx public key: 5c11f7acd05ccc6e074a18af022c3fbb5270156f6effd7a38f8490f12f1219f5
Timestamp: 1712874110 Timestamp [UCT]: 2024-04-11 22:21:50 Age [y:d:h:m:s]: 01:206:02:59:36
Block: 998452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406003 RingCT/type: yes/0
Extra: 015c11f7acd05ccc6e074a18af022c3fbb5270156f6effd7a38f8490f12f1219f50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a09c95cfabf5846d74bb09a441a60188da1115682a17a3aaad2641a394364d9 0.600000000000 1458902 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": 998462, "vin": [ { "gen": { "height": 998452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a09c95cfabf5846d74bb09a441a60188da1115682a17a3aaad2641a394364d9" } } ], "extra": [ 1, 92, 17, 247, 172, 208, 92, 204, 110, 7, 74, 24, 175, 2, 44, 63, 187, 82, 112, 21, 111, 110, 255, 215, 163, 143, 132, 144, 241, 47, 18, 25, 245, 2, 17, 0, 0, 0, 3, 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