Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b833322b01cd6833dbf8d344b7a42eb5ab3b23fee835eba9fd9d89a5768e5679

Tx prefix hash: a61d2d05b47130c31294ac9015513aeb02448c76575df33eb368ff61ab0ea091
Tx public key: 05e3be0c50f0d182d44476527c4e7c94030f6c2843b00fd90e01afa8ef6d1a28
Timestamp: 1740966275 Timestamp [UCT]: 2025-03-03 01:44:35 Age [y:d:h:m:s]: 00:261:18:08:13
Block: 1230910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184831 RingCT/type: yes/0
Extra: 0105e3be0c50f0d182d44476527c4e7c94030f6c2843b00fd90e01afa8ef6d1a280211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0efadcfd5577e79ac950a2d46bd3d6cce76b1bf27e364311f7063bd6c1dfa2a2 0.600000000000 1717813 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": 1230920, "vin": [ { "gen": { "height": 1230910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0efadcfd5577e79ac950a2d46bd3d6cce76b1bf27e364311f7063bd6c1dfa2a2" } } ], "extra": [ 1, 5, 227, 190, 12, 80, 240, 209, 130, 212, 68, 118, 82, 124, 78, 124, 148, 3, 15, 108, 40, 67, 176, 15, 217, 14, 1, 175, 168, 239, 109, 26, 40, 2, 17, 0, 0, 0, 4, 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