Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d40b0db01df5010a0925fbd8aabe8f9ae0e8d5f10bd25bc2e031b7b4deaacd3

Tx prefix hash: 5e57dd7b94622f649431a19f6e2a96d1e2567642f84930a60a6272475cc52bf1
Tx public key: 8b7891176ebd1a3158a128cd64ec10208e479623b80427a47e9f1932ba2087a4
Timestamp: 1712795572 Timestamp [UCT]: 2024-04-11 00:32:52 Age [y:d:h:m:s]: 01:203:22:13:00
Block: 997803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404433 RingCT/type: yes/0
Extra: 018b7891176ebd1a3158a128cd64ec10208e479623b80427a47e9f1932ba2087a402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce707aef6d315bc5520636a585c7d340aea4fd9cd67afdd4a931cf6f1244dee4 0.600000000000 1458237 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": 997813, "vin": [ { "gen": { "height": 997803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce707aef6d315bc5520636a585c7d340aea4fd9cd67afdd4a931cf6f1244dee4" } } ], "extra": [ 1, 139, 120, 145, 23, 110, 189, 26, 49, 88, 161, 40, 205, 100, 236, 16, 32, 142, 71, 150, 35, 184, 4, 39, 164, 126, 159, 25, 50, 186, 32, 135, 164, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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