Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddf70826b8904eddd8e6f83ea060397711d62ddc8473b9a965402d5e7bd7e47e

Tx prefix hash: 234b43f195e77b6477b9e7601aeb03aba4f4a482e222d8c635a200b03659e5a0
Tx public key: c273a0f8a2af79f6714d85df2101ac40f13dcff62cef202be8ac113b501b4cc6
Timestamp: 1721525698 Timestamp [UCT]: 2024-07-21 01:34:58 Age [y:d:h:m:s]: 00:270:04:17:29
Block: 1070208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193023 RingCT/type: yes/0
Extra: 01c273a0f8a2af79f6714d85df2101ac40f13dcff62cef202be8ac113b501b4cc602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 722d92d2de515b6eb80b6fd2bbfcda65339a7169867bdb01a85c841db249df9e 0.600000000000 1541945 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": 1070218, "vin": [ { "gen": { "height": 1070208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "722d92d2de515b6eb80b6fd2bbfcda65339a7169867bdb01a85c841db249df9e" } } ], "extra": [ 1, 194, 115, 160, 248, 162, 175, 121, 246, 113, 77, 133, 223, 33, 1, 172, 64, 241, 61, 207, 246, 44, 239, 32, 43, 232, 172, 17, 59, 80, 27, 76, 198, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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