Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d8de89dd60f88475d9b56380f54f3ccf369c8a7409464bec984109098eb0f5b

Tx prefix hash: 4bd9f53154dbbd81fffbd421d03b9a9fdaf9099ce1c77e1c2ee5f015f9e45948
Tx public key: a4a54765d7a54df620816984d241a7394c3c61e2f507e2bc845f81997c99f495
Timestamp: 1701947501 Timestamp [UCT]: 2023-12-07 11:11:41 Age [y:d:h:m:s]: 01:152:02:58:32
Block: 907895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369890 RingCT/type: yes/0
Extra: 01a4a54765d7a54df620816984d241a7394c3c61e2f507e2bc845f81997c99f49502110000000233af99f4000000000000000000

1 output(s) for total of 0.602236331000 dcy

stealth address amount amount idx
00: 62eced7c9eec43bd4fb410312d747dc2b4d8151be44faa4fbd86865ff88cc643 0.602236331000 1364892 of 0

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": 907905, "vin": [ { "gen": { "height": 907895 } } ], "vout": [ { "amount": 602236331, "target": { "key": "62eced7c9eec43bd4fb410312d747dc2b4d8151be44faa4fbd86865ff88cc643" } } ], "extra": [ 1, 164, 165, 71, 101, 215, 165, 77, 246, 32, 129, 105, 132, 210, 65, 167, 57, 76, 60, 97, 226, 245, 7, 226, 188, 132, 95, 129, 153, 124, 153, 244, 149, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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