Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34f91f05a416a093526f5fc6ed8df3e21f2bb57b6412022ec9882da1e7940ff8

Tx prefix hash: b072440bb39ecdd541e150fdea2f9059e7ab955464f384d78cffe685bb21633a
Tx public key: 1541cfc8a292b1aa9d4b3e3400ee864a60e9fb653880aef5298851305f03af9d
Timestamp: 1696842586 Timestamp [UCT]: 2023-10-09 09:09:46 Age [y:d:h:m:s]: 01:197:16:40:19
Block: 865780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402326 RingCT/type: yes/0
Extra: 011541cfc8a292b1aa9d4b3e3400ee864a60e9fb653880aef5298851305f03af9d02110000000136a45730000000000000000000

1 output(s) for total of 0.830446179000 dcy

stealth address amount amount idx
00: 40c0d33b344f3bd73035f08869f827e1304d3e1b11abd1dc7e94ef78db7f3d4d 0.830446179000 1320328 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": 865790, "vin": [ { "gen": { "height": 865780 } } ], "vout": [ { "amount": 830446179, "target": { "key": "40c0d33b344f3bd73035f08869f827e1304d3e1b11abd1dc7e94ef78db7f3d4d" } } ], "extra": [ 1, 21, 65, 207, 200, 162, 146, 177, 170, 157, 75, 62, 52, 0, 238, 134, 74, 96, 233, 251, 101, 56, 128, 174, 245, 41, 136, 81, 48, 95, 3, 175, 157, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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