Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49113b4368bd7120c1732da997d817582b9422a424b179792fe0d096dc567d87

Tx prefix hash: 1626b65aa104ef6a86a771ae71a5031c88a5ca9e462da6ca7dbae2fc45220a17
Tx public key: 1b70a26fb575e9e9d597af0581ed41e61fd9b03074e6559919282e5f7142d926
Timestamp: 1727998473 Timestamp [UCT]: 2024-10-03 23:34:33 Age [y:d:h:m:s]: 00:204:01:14:35
Block: 1123866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145630 RingCT/type: yes/0
Extra: 011b70a26fb575e9e9d597af0581ed41e61fd9b03074e6559919282e5f7142d92602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee26eb907042a1cf48b0ab4c34ff21e7c64f5fe1dfdea0d11764d5b69adb8c5c 0.600000000000 1606407 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": 1123876, "vin": [ { "gen": { "height": 1123866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee26eb907042a1cf48b0ab4c34ff21e7c64f5fe1dfdea0d11764d5b69adb8c5c" } } ], "extra": [ 1, 27, 112, 162, 111, 181, 117, 233, 233, 213, 151, 175, 5, 129, 237, 65, 230, 31, 217, 176, 48, 116, 230, 85, 153, 25, 40, 46, 95, 113, 66, 217, 38, 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