Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 849a6b33ffae6b7a36862c8b79869f2cb9b23b25e1c054a732002967a51fa9aa

Tx prefix hash: 40e393b5123b49dd52ae0beb9b777dbd32c8f85b4154d19b9656c71d9f5e7c03
Tx public key: c72a13fff6cf6cbfbe02893fa889bf4dca8ee4c8f9183ba52152d5a116bb7080
Timestamp: 1726333018 Timestamp [UCT]: 2024-09-14 16:56:58 Age [y:d:h:m:s]: 00:115:03:24:47
Block: 1110057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82344 RingCT/type: yes/0
Extra: 01c72a13fff6cf6cbfbe02893fa889bf4dca8ee4c8f9183ba52152d5a116bb7080021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b8b2280e93b5b211807e595a2f7fd4f0e2a74ba2b24fc2528f02c53574d4155 0.600000000000 1588530 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": 1110067, "vin": [ { "gen": { "height": 1110057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b8b2280e93b5b211807e595a2f7fd4f0e2a74ba2b24fc2528f02c53574d4155" } } ], "extra": [ 1, 199, 42, 19, 255, 246, 207, 108, 191, 190, 2, 137, 63, 168, 137, 191, 77, 202, 142, 228, 200, 249, 24, 59, 165, 33, 82, 213, 161, 22, 187, 112, 128, 2, 17, 0, 0, 0, 9, 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