Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25751b40edae82c8fe1d7bae8b6d8e9150e8607ca3228c2f62374f3057779519

Tx prefix hash: 37db4f7b3b05aa481f672b62f4fd3fc602dafb5765036594dfb13dc6acd042d1
Tx public key: 43341e1300c8680e8f81fa0302b178940b53e4763cd762113493c5c31ac689e2
Timestamp: 1699477580 Timestamp [UCT]: 2023-11-08 21:06:20 Age [y:d:h:m:s]: 01:138:14:14:16
Block: 887422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360212 RingCT/type: yes/0
Extra: 0143341e1300c8680e8f81fa0302b178940b53e4763cd762113493c5c31ac689e2021100000006faf35c9c000000000000000000

1 output(s) for total of 0.704048422000 dcy

stealth address amount amount idx
00: a1a3270d99a565b2ec961e6e30ea76300e501d4efb17bf7a90b3d0c768c15832 0.704048422000 1343305 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": 887432, "vin": [ { "gen": { "height": 887422 } } ], "vout": [ { "amount": 704048422, "target": { "key": "a1a3270d99a565b2ec961e6e30ea76300e501d4efb17bf7a90b3d0c768c15832" } } ], "extra": [ 1, 67, 52, 30, 19, 0, 200, 104, 14, 143, 129, 250, 3, 2, 177, 120, 148, 11, 83, 228, 118, 60, 215, 98, 17, 52, 147, 197, 195, 26, 198, 137, 226, 2, 17, 0, 0, 0, 6, 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