Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b99943aec4a2da61d373b7d2a2e51186071f9d3ac098c5e32498b65c8462476f

Tx prefix hash: bb53100a42f485d596c14bece8b56ef6a8d953b17cc4cb638645aa83cea40866
Tx public key: c7dbdc949512dd49668872253196d565a56712a0d4b3fd6c20c69964996d4486
Timestamp: 1725800198 Timestamp [UCT]: 2024-09-08 12:56:38 Age [y:d:h:m:s]: 00:233:23:05:03
Block: 1105646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167072 RingCT/type: yes/0
Extra: 01c7dbdc949512dd49668872253196d565a56712a0d4b3fd6c20c69964996d4486021100000004e914dd15000000000000000000

1 output(s) for total of 0.607820000000 dcy

stealth address amount amount idx
00: 481bfecfd543d76721f6f30877296e9ae3efa521e5ac39f354ea2d4474132127 0.607820000000 1583049 of 0

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": 1105656, "vin": [ { "gen": { "height": 1105646 } } ], "vout": [ { "amount": 607820000, "target": { "key": "481bfecfd543d76721f6f30877296e9ae3efa521e5ac39f354ea2d4474132127" } } ], "extra": [ 1, 199, 219, 220, 148, 149, 18, 221, 73, 102, 136, 114, 37, 49, 150, 213, 101, 165, 103, 18, 160, 212, 179, 253, 108, 32, 198, 153, 100, 153, 109, 68, 134, 2, 17, 0, 0, 0, 4, 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