Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77c4f9618fd638f5f5656f47230e7c7c690f67d55717c3626e624b20c0dbed42

Tx prefix hash: 99a2278b1ce18328c73cce5a9f459471c494c8cfaeb2b04d763fedf07573f940
Tx public key: 1f4a9859a58d0cab0e9b55c0f855ca19812228c51df22ad31211873ac14f061d
Timestamp: 1735459985 Timestamp [UCT]: 2024-12-29 08:13:05 Age [y:d:h:m:s]: 00:170:13:12:22
Block: 1185592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121613 RingCT/type: yes/0
Extra: 011f4a9859a58d0cab0e9b55c0f855ca19812228c51df22ad31211873ac14f061d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da5eb922c16806ea98885d190523881ba07245e1d297f3fb44e58dcb4c0f2717 0.600000000000 1672067 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": 1185602, "vin": [ { "gen": { "height": 1185592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da5eb922c16806ea98885d190523881ba07245e1d297f3fb44e58dcb4c0f2717" } } ], "extra": [ 1, 31, 74, 152, 89, 165, 141, 12, 171, 14, 155, 85, 192, 248, 85, 202, 25, 129, 34, 40, 197, 29, 242, 42, 211, 18, 17, 135, 58, 193, 79, 6, 29, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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