Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf382a2ab811cafc21f3c5e2e2d6e319982f804dbb82f015b66da5d305ca0f7d

Tx prefix hash: 4ef270aea7ce64ece103ae619fc60dd933771a7752597079d9a2f36d6545f15a
Tx public key: 65b754b731ec08b2dc701b6bf0000f79f2943d42c2c45b52511d46fd50ad4392
Timestamp: 1703209690 Timestamp [UCT]: 2023-12-22 01:48:10 Age [y:d:h:m:s]: 01:019:00:57:11
Block: 918350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274958 RingCT/type: yes/0
Extra: 0165b754b731ec08b2dc701b6bf0000f79f2943d42c2c45b52511d46fd50ad439202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 635414d12cf67aa886be508fc90da5f5796dc8fdc48512f61b947557fb9a54ed 0.600000000000 1375992 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": 918360, "vin": [ { "gen": { "height": 918350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "635414d12cf67aa886be508fc90da5f5796dc8fdc48512f61b947557fb9a54ed" } } ], "extra": [ 1, 101, 183, 84, 183, 49, 236, 8, 178, 220, 112, 27, 107, 240, 0, 15, 121, 242, 148, 61, 66, 194, 196, 91, 82, 81, 29, 70, 253, 80, 173, 67, 146, 2, 17, 0, 0, 0, 2, 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