Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b028cc414a96985c6d6244a3798dc234595d4d514ab223ce5971f6c5c7e62a16

Tx prefix hash: 7e327b56dea8c7da136f88585b11ab783d99b94d0db748ae87a40a254595f472
Tx public key: c2b4f83e6bca13adaa947365780ae06ce519bcbebe1f52d9afe53873e9d94461
Timestamp: 1714094859 Timestamp [UCT]: 2024-04-26 01:27:39 Age [y:d:h:m:s]: 00:304:22:11:58
Block: 1008588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217960 RingCT/type: yes/0
Extra: 01c2b4f83e6bca13adaa947365780ae06ce519bcbebe1f52d9afe53873e9d9446102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6b5bb0f24a5e8f91ae6a486c0b6567c67ef3fc1b282c9790a9ad67874e80975 0.600000000000 1470060 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": 1008598, "vin": [ { "gen": { "height": 1008588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6b5bb0f24a5e8f91ae6a486c0b6567c67ef3fc1b282c9790a9ad67874e80975" } } ], "extra": [ 1, 194, 180, 248, 62, 107, 202, 19, 173, 170, 148, 115, 101, 120, 10, 224, 108, 229, 25, 188, 190, 190, 31, 82, 217, 175, 229, 56, 115, 233, 217, 68, 97, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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