Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f12d6cf240279e9d8f6a262822221729275b488994e6b8a4900e0dcd4c9a5503

Tx prefix hash: b44d8045ce132fdd22c91bb6e2418eeb6a4d2b0db2ca9e8aeca1d65cb8d0fa29
Tx public key: b10f95f03358f63b34e5252be5f508604f0fadac816cbbe14a434a40d80dc069
Timestamp: 1735006406 Timestamp [UCT]: 2024-12-24 02:13:26 Age [y:d:h:m:s]: 00:099:14:17:11
Block: 1181856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70955 RingCT/type: yes/0
Extra: 01b10f95f03358f63b34e5252be5f508604f0fadac816cbbe14a434a40d80dc0690211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c49db5d89c7d659c7c2dd8fbda8c30e191ce2c6e0a6096385837192808481d96 0.600000000000 1668285 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": 1181866, "vin": [ { "gen": { "height": 1181856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c49db5d89c7d659c7c2dd8fbda8c30e191ce2c6e0a6096385837192808481d96" } } ], "extra": [ 1, 177, 15, 149, 240, 51, 88, 246, 59, 52, 229, 37, 43, 229, 245, 8, 96, 79, 15, 173, 172, 129, 108, 187, 225, 74, 67, 74, 64, 216, 13, 192, 105, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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