Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfdb59d3049e7d212a15fd8e4544441e445a778403444d09a3eafa4ca5f46bf0

Tx prefix hash: 628f8a77b5f37fa6798aef593d3cf7e267d3b8b34dde8df5cf7693ae746c87a7
Tx public key: 79fb221c817975e9dc1547aee9283584663001f7da2a6d81989524e0e4a10bb5
Timestamp: 1696708468 Timestamp [UCT]: 2023-10-07 19:54:28 Age [y:d:h:m:s]: 02:032:19:48:05
Block: 864656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543086 RingCT/type: yes/0
Extra: 0179fb221c817975e9dc1547aee9283584663001f7da2a6d81989524e0e4a10bb502110000000475e3f0e9000000000000000000

1 output(s) for total of 0.837598269000 dcy

stealth address amount amount idx
00: d535eb67af90b5c1cc2858d7884a02729c4e50d553a8f66173004d39ba6e22fd 0.837598269000 1319176 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": 864666, "vin": [ { "gen": { "height": 864656 } } ], "vout": [ { "amount": 837598269, "target": { "key": "d535eb67af90b5c1cc2858d7884a02729c4e50d553a8f66173004d39ba6e22fd" } } ], "extra": [ 1, 121, 251, 34, 28, 129, 121, 117, 233, 220, 21, 71, 174, 233, 40, 53, 132, 102, 48, 1, 247, 218, 42, 109, 129, 152, 149, 36, 224, 228, 161, 11, 181, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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