Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351fea44d4d82a82c2c3b75d6e9e858099fe9381b90da0d258c8a0506e42edad

Tx prefix hash: 0b455011ad0a92fa38c901ac7b5bf82bd9f2f356b854d6d9f22dabf9d5aa88cd
Tx public key: bbf7ea7800e045b0945597c13169bc962165a426b0545dc446ca95510e0a84b3
Timestamp: 1725122989 Timestamp [UCT]: 2024-08-31 16:49:49 Age [y:d:h:m:s]: 00:075:19:01:29
Block: 1100027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54197 RingCT/type: yes/0
Extra: 01bbf7ea7800e045b0945597c13169bc962165a426b0545dc446ca95510e0a84b3021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6724ecd3a65dd030e9b34e4ef086704951bcc5d5562de4e7d7cfddf6a27d5230 0.600000000000 1575998 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": 1100037, "vin": [ { "gen": { "height": 1100027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6724ecd3a65dd030e9b34e4ef086704951bcc5d5562de4e7d7cfddf6a27d5230" } } ], "extra": [ 1, 187, 247, 234, 120, 0, 224, 69, 176, 148, 85, 151, 193, 49, 105, 188, 150, 33, 101, 164, 38, 176, 84, 93, 196, 70, 202, 149, 81, 14, 10, 132, 179, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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