Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bdb18eb9eeced8ef416c83bb2b7751387171853448dd9eb7b5fc9a4a75c2411

Tx prefix hash: aae40a9796034970a37a1fa9d6eb40ff8248f12f6f1d3c6c20f2f23efa22c62a
Tx public key: 44a11f537fa584324ec6704e7d2639b6f9975a1b7885ab17e68238c1ca33b2b7
Timestamp: 1712641815 Timestamp [UCT]: 2024-04-09 05:50:15 Age [y:d:h:m:s]: 01:068:07:02:43
Block: 996527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309724 RingCT/type: yes/0
Extra: 0144a11f537fa584324ec6704e7d2639b6f9975a1b7885ab17e68238c1ca33b2b7021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddf1a21afed36642bc49f52a5eef7859317b3d6df5390b52eb93a412f0b20710 0.600000000000 1456947 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": 996537, "vin": [ { "gen": { "height": 996527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf1a21afed36642bc49f52a5eef7859317b3d6df5390b52eb93a412f0b20710" } } ], "extra": [ 1, 68, 161, 31, 83, 127, 165, 132, 50, 78, 198, 112, 78, 125, 38, 57, 182, 249, 151, 90, 27, 120, 133, 171, 23, 230, 130, 56, 193, 202, 51, 178, 183, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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