Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fefac4dfc7a2cb3155af01e3233fdeb35b913af5a280a48cb38d6dd3cc3fd01b

Tx prefix hash: 8f6cfe5ba5ed93703ed1b1e4f3917ac24584d42b0e075479889dddfe9d35d95d
Tx public key: df6f8b6b07268536407c86902be8cb9d512ee7ef9954a7ab3b5613edad90e5cd
Timestamp: 1710252347 Timestamp [UCT]: 2024-03-12 14:05:47 Age [y:d:h:m:s]: 00:291:21:47:12
Block: 976758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208939 RingCT/type: yes/0
Extra: 01df6f8b6b07268536407c86902be8cb9d512ee7ef9954a7ab3b5613edad90e5cd02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5598405463d0282746391fbb940b62fd944e32e1789eab380d55086348975d26 0.600000000000 1436753 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": 976768, "vin": [ { "gen": { "height": 976758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5598405463d0282746391fbb940b62fd944e32e1789eab380d55086348975d26" } } ], "extra": [ 1, 223, 111, 139, 107, 7, 38, 133, 54, 64, 124, 134, 144, 43, 232, 203, 157, 81, 46, 231, 239, 153, 84, 167, 171, 59, 86, 19, 237, 173, 144, 229, 205, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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