Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f11426cfaaa2bfbfb25a394fae7d5bc15d4287d6fa87ef840e23825dd7bd0d3

Tx prefix hash: 1c96f1f7fefcd80e8df3e3753e95980e3a8879e5da4ed6aaa799a48b7bcb7e59
Tx public key: 4efa19a2b334b11867f893e671c304aec2328f496bb13d34393b8013ea49fb12
Timestamp: 1707671635 Timestamp [UCT]: 2024-02-11 17:13:55 Age [y:d:h:m:s]: 01:015:00:01:02
Block: 955345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271732 RingCT/type: yes/0
Extra: 014efa19a2b334b11867f893e671c304aec2328f496bb13d34393b8013ea49fb120211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d01cb0300ad2e37065f20685a76bd6a002be4e8edee019f6d91054cbb19bd8e4 0.600000000000 1414633 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": 955355, "vin": [ { "gen": { "height": 955345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d01cb0300ad2e37065f20685a76bd6a002be4e8edee019f6d91054cbb19bd8e4" } } ], "extra": [ 1, 78, 250, 25, 162, 179, 52, 177, 24, 103, 248, 147, 230, 113, 195, 4, 174, 194, 50, 143, 73, 107, 177, 61, 52, 57, 59, 128, 19, 234, 73, 251, 18, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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