Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f04ba1c27445989f7ac8b036f26b9dc3ccec7a541749c39b78d719df32902981

Tx prefix hash: d333ea36f04b18ff9ecc8ff918da939683b3ef96f15cd79aacd6a92df218fb8a
Tx public key: 95d5f18e2b4cfb5e9b7712bb8353d9c80fa57f8d32e311f2670836b45f164200
Timestamp: 1681965934 Timestamp [UCT]: 2023-04-20 04:45:34 Age [y:d:h:m:s]: 01:354:08:37:59
Block: 742484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514517 RingCT/type: yes/0
Extra: 0195d5f18e2b4cfb5e9b7712bb8353d9c80fa57f8d32e311f2670836b45f164200021100000006b3164c24000000000000000000

1 output(s) for total of 2.127367413000 dcy

stealth address amount amount idx
00: 02bcf2ef659eba1e3475c7d7c98a91acf3a5982f3fa20d51c32c6d24f05a15e9 2.127367413000 1189457 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": 742494, "vin": [ { "gen": { "height": 742484 } } ], "vout": [ { "amount": 2127367413, "target": { "key": "02bcf2ef659eba1e3475c7d7c98a91acf3a5982f3fa20d51c32c6d24f05a15e9" } } ], "extra": [ 1, 149, 213, 241, 142, 43, 76, 251, 94, 155, 119, 18, 187, 131, 83, 217, 200, 15, 165, 127, 141, 50, 227, 17, 242, 103, 8, 54, 180, 95, 22, 66, 0, 2, 17, 0, 0, 0, 6, 179, 22, 76, 36, 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