Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed4ab7d3cecfcfa1179bf2a8a2f80cbfb03b0876e8fb2da12441fc1b0442f0dd

Tx prefix hash: a4f59529e3505fc0fe0a1115fc06d77247302d3e86f1b93cd462d1cf17d58133
Tx public key: 65ebbd53c1e7f614acc2e17cdedb79b28992523d053bd446bcae2837a6497888
Timestamp: 1712201499 Timestamp [UCT]: 2024-04-04 03:31:39 Age [y:d:h:m:s]: 00:293:16:32:59
Block: 992870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210212 RingCT/type: yes/0
Extra: 0165ebbd53c1e7f614acc2e17cdedb79b28992523d053bd446bcae2837a64978880211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d21ba05d02055740b351d8d58cc1eae505972c915da09a0c6407eb96e8efe18 0.600000000000 1453246 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": 992880, "vin": [ { "gen": { "height": 992870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d21ba05d02055740b351d8d58cc1eae505972c915da09a0c6407eb96e8efe18" } } ], "extra": [ 1, 101, 235, 189, 83, 193, 231, 246, 20, 172, 194, 225, 124, 222, 219, 121, 178, 137, 146, 82, 61, 5, 59, 212, 70, 188, 174, 40, 55, 166, 73, 120, 136, 2, 17, 0, 0, 0, 4, 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