Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b2756ed3262d181b902f55fc0a7c0b05248fdbd46ff1538089aa4add2d21db8

Tx prefix hash: 24a2b81e489c661ec86b4d51e81ef4cc3752b9ef97818c1b7adc5572380f608c
Tx public key: 8aaa5279599b7656e2d9420e0a3bb33c4485e9c15bfeaa2ac65774dc40f60959
Timestamp: 1717984244 Timestamp [UCT]: 2024-06-10 01:50:44 Age [y:d:h:m:s]: 01:006:16:56:13
Block: 1040850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265575 RingCT/type: yes/0
Extra: 018aaa5279599b7656e2d9420e0a3bb33c4485e9c15bfeaa2ac65774dc40f609590211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 325505580eeab1fe409e9c9df63fdb22431cfc7782340a90b60a39a60f7d5ebc 0.600000000000 1509513 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": 1040860, "vin": [ { "gen": { "height": 1040850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "325505580eeab1fe409e9c9df63fdb22431cfc7782340a90b60a39a60f7d5ebc" } } ], "extra": [ 1, 138, 170, 82, 121, 89, 155, 118, 86, 226, 217, 66, 14, 10, 59, 179, 60, 68, 133, 233, 193, 91, 254, 170, 42, 198, 87, 116, 220, 64, 246, 9, 89, 2, 17, 0, 0, 0, 3, 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