Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d853dafbf0840e14b8fc90cf94fe7b41e96425fe2aaaa38ff15e1e53fa6935b

Tx prefix hash: b1ebab4d8f7d943364b92243391ac4d7296a8d3bb9f6783161a08147fe12d3df
Tx public key: 022a96ff0054594b375ab64ecec5591dc9a983e0e23fbe42c8c0fce60712670b
Timestamp: 1715294063 Timestamp [UCT]: 2024-05-09 22:34:23 Age [y:d:h:m:s]: 00:340:22:12:34
Block: 1018542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243694 RingCT/type: yes/0
Extra: 01022a96ff0054594b375ab64ecec5591dc9a983e0e23fbe42c8c0fce60712670b02110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d36360a3511e72c7ac302d1d00d4f4c78d749817cbb16dc8b57a799f26413e6a 0.600000000000 1482333 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": 1018552, "vin": [ { "gen": { "height": 1018542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d36360a3511e72c7ac302d1d00d4f4c78d749817cbb16dc8b57a799f26413e6a" } } ], "extra": [ 1, 2, 42, 150, 255, 0, 84, 89, 75, 55, 90, 182, 78, 206, 197, 89, 29, 201, 169, 131, 224, 226, 63, 190, 66, 200, 192, 252, 230, 7, 18, 103, 11, 2, 17, 0, 0, 0, 16, 89, 218, 211, 245, 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