Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa2c6f1653d0de3ccf1b2e090bc071d29036a9df4f34c1ed220013963f1968c5

Tx prefix hash: f7718dcd23e336675ea239161d113b7818312db1e275463f6edd28c95a5e802a
Tx public key: 6c87994c72749dd9b04311574bdd792b949dd349f9e42da181add3d2f286a974
Timestamp: 1698650039 Timestamp [UCT]: 2023-10-30 07:13:59 Age [y:d:h:m:s]: 01:157:20:20:03
Block: 880767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373800 RingCT/type: yes/0
Extra: 016c87994c72749dd9b04311574bdd792b949dd349f9e42da181add3d2f286a974021100000003faf35c9c000000000000000000

1 output(s) for total of 0.740718713000 dcy

stealth address amount amount idx
00: 6f8ffa0f3be2efd5e9fd81ea41e2e1d9cd17f24a5ca408c95d809fd1b98bfb3f 0.740718713000 1336333 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": 880777, "vin": [ { "gen": { "height": 880767 } } ], "vout": [ { "amount": 740718713, "target": { "key": "6f8ffa0f3be2efd5e9fd81ea41e2e1d9cd17f24a5ca408c95d809fd1b98bfb3f" } } ], "extra": [ 1, 108, 135, 153, 76, 114, 116, 157, 217, 176, 67, 17, 87, 75, 221, 121, 43, 148, 157, 211, 73, 249, 228, 45, 161, 129, 173, 211, 210, 242, 134, 169, 116, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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