Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f145dcfbfd1f407567aa327485fb7aaeef67137ac25b17ed67c8ea6e40fe5551

Tx prefix hash: 969f6971dca46820da7bda4ea069214eb2ba86f620f75ccb883d0514b5bc6451
Tx public key: e99b5eb0f53ac283496d0425c639580ab857ae325191e3cac6f259a92c7b92fe
Timestamp: 1711174676 Timestamp [UCT]: 2024-03-23 06:17:56 Age [y:d:h:m:s]: 00:221:13:10:20
Block: 984414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158597 RingCT/type: yes/0
Extra: 01e99b5eb0f53ac283496d0425c639580ab857ae325191e3cac6f259a92c7b92fe0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4c2ca0365a767ccc2622bbb52c0032599cadc53a9cdae1822651278c5ec84b3 0.600000000000 1444585 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": 984424, "vin": [ { "gen": { "height": 984414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4c2ca0365a767ccc2622bbb52c0032599cadc53a9cdae1822651278c5ec84b3" } } ], "extra": [ 1, 233, 155, 94, 176, 245, 58, 194, 131, 73, 109, 4, 37, 198, 57, 88, 10, 184, 87, 174, 50, 81, 145, 227, 202, 198, 242, 89, 169, 44, 123, 146, 254, 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