Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aef48364e9d648d53a6ca2ee0dbc7090c9ee676de273d1b97930ab2a08cc06df

Tx prefix hash: abaf62a34ed685b3d0043104645cdd2ff8c30a2759ac252dfbe0c9239cae8a60
Tx public key: 7f1b806a6d3d791459309bb6b21e754faf6ff083c5b59b54fc9751760d75e2a7
Timestamp: 1700459641 Timestamp [UCT]: 2023-11-20 05:54:01 Age [y:d:h:m:s]: 01:137:13:03:01
Block: 895550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359478 RingCT/type: yes/0
Extra: 017f1b806a6d3d791459309bb6b21e754faf6ff083c5b59b54fc9751760d75e2a7021100000002faf35c9c000000000000000000

1 output(s) for total of 0.661715152000 dcy

stealth address amount amount idx
00: d1cd45e6015a93f8f76d2ce19c0fd3c475e70a9aa5d897b2113f4c055d875c63 0.661715152000 1351787 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": 895560, "vin": [ { "gen": { "height": 895550 } } ], "vout": [ { "amount": 661715152, "target": { "key": "d1cd45e6015a93f8f76d2ce19c0fd3c475e70a9aa5d897b2113f4c055d875c63" } } ], "extra": [ 1, 127, 27, 128, 106, 109, 61, 121, 20, 89, 48, 155, 182, 178, 30, 117, 79, 175, 111, 240, 131, 197, 181, 155, 84, 252, 151, 81, 118, 13, 117, 226, 167, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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