Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2d4b60faa4ff811f27153392d2fd36e8ac6af876ba755689c3e7a520c51d8f

Tx prefix hash: f023e14678c2b5a5ea8913c6be9049b9ea0a4367df3e240874e0572e815bb870
Tx public key: ec2a70ce6efe4e7995040cab90bda8878075782bdfd9f5d964c190f8f6e7db86
Timestamp: 1724012320 Timestamp [UCT]: 2024-08-18 20:18:40 Age [y:d:h:m:s]: 00:238:19:00:45
Block: 1090825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170539 RingCT/type: yes/0
Extra: 01ec2a70ce6efe4e7995040cab90bda8878075782bdfd9f5d964c190f8f6e7db8602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91307e2575466619e597ff985036a4ed0f481a22f675d31dde12b3e8438ae4e3 0.600000000000 1565450 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": 1090835, "vin": [ { "gen": { "height": 1090825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91307e2575466619e597ff985036a4ed0f481a22f675d31dde12b3e8438ae4e3" } } ], "extra": [ 1, 236, 42, 112, 206, 110, 254, 78, 121, 149, 4, 12, 171, 144, 189, 168, 135, 128, 117, 120, 43, 223, 217, 245, 217, 100, 193, 144, 248, 246, 231, 219, 134, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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