Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 869a699a39cf223060322716bb61ea2dc85fbb0e86c7dd23b4910224f0deaa09

Tx prefix hash: d4b1254a95280e43389cab34fd6f2281f7f3fe96a5d50ad845ed545690693cad
Tx public key: b5e4422ecc351b49ee732f89863ea7637af19b7dc050721916beb8c9a23ae7be
Timestamp: 1727772855 Timestamp [UCT]: 2024-10-01 08:54:15 Age [y:d:h:m:s]: 00:180:19:11:12
Block: 1122003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129000 RingCT/type: yes/0
Extra: 01b5e4422ecc351b49ee732f89863ea7637af19b7dc050721916beb8c9a23ae7be021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d53383326c7d27b373db63661a4ce525d4a3c097db8f01d2ec762506de135c7e 0.600000000000 1604368 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": 1122013, "vin": [ { "gen": { "height": 1122003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d53383326c7d27b373db63661a4ce525d4a3c097db8f01d2ec762506de135c7e" } } ], "extra": [ 1, 181, 228, 66, 46, 204, 53, 27, 73, 238, 115, 47, 137, 134, 62, 167, 99, 122, 241, 155, 125, 192, 80, 114, 25, 22, 190, 184, 201, 162, 58, 231, 190, 2, 17, 0, 0, 0, 6, 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