Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b4ab2925363da8ad095c0d74ddd44bbf816adf45322f1ff273d795331f218b

Tx prefix hash: 5e933278a6477dbdb3ef7160961267c7f1ced9cd9f22d52805290661ecf0af38
Tx public key: fc19309d7cb4d638c8a1f3d53d2f6a15a4515a76cf6b3dd551e049995a37ded8
Timestamp: 1710360917 Timestamp [UCT]: 2024-03-13 20:15:17 Age [y:d:h:m:s]: 01:018:11:59:11
Block: 977663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274189 RingCT/type: yes/0
Extra: 01fc19309d7cb4d638c8a1f3d53d2f6a15a4515a76cf6b3dd551e049995a37ded80211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28c228a013943431b1857ef8f03ba616819bd076ca4b37fc6e38e32fec2f8d26 0.600000000000 1437666 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": 977673, "vin": [ { "gen": { "height": 977663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28c228a013943431b1857ef8f03ba616819bd076ca4b37fc6e38e32fec2f8d26" } } ], "extra": [ 1, 252, 25, 48, 157, 124, 180, 214, 56, 200, 161, 243, 213, 61, 47, 106, 21, 164, 81, 90, 118, 207, 107, 61, 213, 81, 224, 73, 153, 90, 55, 222, 216, 2, 17, 0, 0, 0, 9, 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