Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fad2611e0544083ba56aa1c587bfa140752cce60230d5bdcd7cc5a7877e15c9

Tx prefix hash: ecf3b377a7ee1cb5174a368cdc18a879d585b4a692d2751ab643658d74b74f88
Tx public key: 52944f8ff64c063f2dcc290671545a923a613e69a6d52c57084ea666289edfe4
Timestamp: 1721757058 Timestamp [UCT]: 2024-07-23 17:50:58 Age [y:d:h:m:s]: 00:236:18:38:30
Block: 1072109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169160 RingCT/type: yes/0
Extra: 0152944f8ff64c063f2dcc290671545a923a613e69a6d52c57084ea666289edfe402110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 444f12bf2a4ee7fc04faa4d1a3432fc5b4f9eea0ca4fce2fe3b501dc36fcc70d 0.600000000000 1544558 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": 1072119, "vin": [ { "gen": { "height": 1072109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "444f12bf2a4ee7fc04faa4d1a3432fc5b4f9eea0ca4fce2fe3b501dc36fcc70d" } } ], "extra": [ 1, 82, 148, 79, 143, 246, 76, 6, 63, 45, 204, 41, 6, 113, 84, 90, 146, 58, 97, 62, 105, 166, 213, 44, 87, 8, 78, 166, 102, 40, 158, 223, 228, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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