Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a7cfb4749dbfcd3855356bd2103ab38d2497e784a1f53b500880fd8b6fb596

Tx prefix hash: 7496d83a8fc051fb1752e5709c51ae604ce7fe08a9613809fbe4d7dc0e0d5b61
Tx public key: c0ffe81276fffdc6637c18553ad0586a125fbcb73ea371f18ae962f512e15008
Timestamp: 1711849338 Timestamp [UCT]: 2024-03-31 01:42:18 Age [y:d:h:m:s]: 00:299:22:36:54
Block: 989996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214640 RingCT/type: yes/0
Extra: 01c0ffe81276fffdc6637c18553ad0586a125fbcb73ea371f18ae962f512e150080211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b79e0ff576e0bd48e8b49ea015d7d155dc9fffca18aa5d2d96eb047dba460b5d 0.600000000000 1450314 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": 990006, "vin": [ { "gen": { "height": 989996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b79e0ff576e0bd48e8b49ea015d7d155dc9fffca18aa5d2d96eb047dba460b5d" } } ], "extra": [ 1, 192, 255, 232, 18, 118, 255, 253, 198, 99, 124, 24, 85, 58, 208, 88, 106, 18, 95, 188, 183, 62, 163, 113, 241, 138, 233, 98, 245, 18, 225, 80, 8, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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