Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d28c73eaa73bc84bace09c5619def2504cc8ed3b69deaa068a857b4b1b5ed9

Tx prefix hash: 426b28f0589c3e9535f3f399ed3d62ecc38fb6c15c6ca5078e94e1dd120b09df
Tx public key: ae80b200c69b853e0f94f1b37dac954805a22790f2b0384090a4c6758aae5ff8
Timestamp: 1707297730 Timestamp [UCT]: 2024-02-07 09:22:10 Age [y:d:h:m:s]: 01:098:02:13:22
Block: 952231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331199 RingCT/type: yes/0
Extra: 01ae80b200c69b853e0f94f1b37dac954805a22790f2b0384090a4c6758aae5ff80211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 936fc9c5503f56d3b71eaf47ca2b4d672cd6278023fa4cf7e608d992c0ff9c9c 0.600000000000 1411125 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": 952241, "vin": [ { "gen": { "height": 952231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "936fc9c5503f56d3b71eaf47ca2b4d672cd6278023fa4cf7e608d992c0ff9c9c" } } ], "extra": [ 1, 174, 128, 178, 0, 198, 155, 133, 62, 15, 148, 241, 179, 125, 172, 149, 72, 5, 162, 39, 144, 242, 176, 56, 64, 144, 164, 198, 117, 138, 174, 95, 248, 2, 17, 0, 0, 0, 7, 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