Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7202337d948bd58eb8730a7a54cc3adb9e74888818a496b2f4f6aa0ceea0b34d

Tx prefix hash: c71721e97f95ffdf4ac147d52ccbe5331d764ccbc2c96afaccff3c7a24ad93a9
Tx public key: 4e21645ab3372da7830a0dad5b95f804fe713d66f27e78da9b6dff476884553b
Timestamp: 1707624631 Timestamp [UCT]: 2024-02-11 04:10:31 Age [y:d:h:m:s]: 01:071:09:54:10
Block: 954946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312100 RingCT/type: yes/0
Extra: 014e21645ab3372da7830a0dad5b95f804fe713d66f27e78da9b6dff476884553b02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1eeec1c8d2293e2ad2ab1d5d8b374aa0811659c5d3f8fdfa6c270fbd8aa9b73 0.600000000000 1414228 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": 954956, "vin": [ { "gen": { "height": 954946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1eeec1c8d2293e2ad2ab1d5d8b374aa0811659c5d3f8fdfa6c270fbd8aa9b73" } } ], "extra": [ 1, 78, 33, 100, 90, 179, 55, 45, 167, 131, 10, 13, 173, 91, 149, 248, 4, 254, 113, 61, 102, 242, 126, 120, 218, 155, 109, 255, 71, 104, 132, 85, 59, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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