Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc0a9bc27034b3639af72431e7055dafb3e206718e90fad6893958cb6bcc38e

Tx prefix hash: d863ab4bde9c2d3f98b2467640e1ac63fa8b62c0e5e1419053ec5f142fbf528b
Tx public key: d724d1c7812711b5ec2c25ca41e718b8a91f64cd734ee91ce525c44f9500eedd
Timestamp: 1714142510 Timestamp [UCT]: 2024-04-26 14:41:50 Age [y:d:h:m:s]: 00:256:13:50:53
Block: 1008997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183643 RingCT/type: yes/0
Extra: 01d724d1c7812711b5ec2c25ca41e718b8a91f64cd734ee91ce525c44f9500eedd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3d5bf5b3d0b265cd9d34a25177dab85effc470e4d1b13c7f4b533ba60e50db5 0.600000000000 1470533 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": 1009007, "vin": [ { "gen": { "height": 1008997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3d5bf5b3d0b265cd9d34a25177dab85effc470e4d1b13c7f4b533ba60e50db5" } } ], "extra": [ 1, 215, 36, 209, 199, 129, 39, 17, 181, 236, 44, 37, 202, 65, 231, 24, 184, 169, 31, 100, 205, 115, 78, 233, 28, 229, 37, 196, 79, 149, 0, 238, 221, 2, 17, 0, 0, 0, 1, 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