Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebfda783cefe013927b1ec2ce44cbd00ef32158f5e70151083e933b91635b108

Tx prefix hash: 481280b63ddbf58332c545c9efb41881312e8031c0a2862e2520ea583dd85b2e
Tx public key: a91008d98c59310b6f9df14c2ea20c22138b4acd22adf7d1461698846d8b7c17
Timestamp: 1709927237 Timestamp [UCT]: 2024-03-08 19:47:17 Age [y:d:h:m:s]: 01:039:13:32:26
Block: 974052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289274 RingCT/type: yes/0
Extra: 01a91008d98c59310b6f9df14c2ea20c22138b4acd22adf7d1461698846d8b7c170211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d424e9ce197b2f9659c192918d28acacf2a0021c8a260c175a2dd1314fa8e15 0.600000000000 1433997 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": 974062, "vin": [ { "gen": { "height": 974052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d424e9ce197b2f9659c192918d28acacf2a0021c8a260c175a2dd1314fa8e15" } } ], "extra": [ 1, 169, 16, 8, 217, 140, 89, 49, 11, 111, 157, 241, 76, 46, 162, 12, 34, 19, 139, 74, 205, 34, 173, 247, 209, 70, 22, 152, 132, 109, 139, 124, 23, 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