Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09666fadd8bfb9e33e4871bb37b6c9fa16ea2c3f94e2bec0cadc017752200852

Tx prefix hash: ddc75c690d1c0d1309e5d0339e4e8d79e6a94a5f9d5fed0b434c3453d2713af5
Tx public key: deb799fb045bc798f960b217c98e6e41578e704a038e5c9229ba04f869ab53a2
Timestamp: 1712764746 Timestamp [UCT]: 2024-04-10 15:59:06 Age [y:d:h:m:s]: 01:223:16:02:23
Block: 997545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418563 RingCT/type: yes/0
Extra: 01deb799fb045bc798f960b217c98e6e41578e704a038e5c9229ba04f869ab53a202110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a15b106a55d580a4b55740e3ce5e8bba3092ec6c1c5e1dee8ac6700b3be450d 0.600000000000 1457977 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": 997555, "vin": [ { "gen": { "height": 997545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a15b106a55d580a4b55740e3ce5e8bba3092ec6c1c5e1dee8ac6700b3be450d" } } ], "extra": [ 1, 222, 183, 153, 251, 4, 91, 199, 152, 249, 96, 178, 23, 201, 142, 110, 65, 87, 142, 112, 74, 3, 142, 92, 146, 41, 186, 4, 248, 105, 171, 83, 162, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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