Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa2d33c57c1c06b549f7341843ec9cdf2da921fe62014902066e9e245e10df1

Tx prefix hash: f49357e1a88b45c9159be8ad98165948b6c021dfb502601bd01b4b4d7294b8a9
Tx public key: d65d7df5086adc654c6a77d15f494a12e525d0a56fbcdbd5cfd7a514fb7fda0b
Timestamp: 1722791018 Timestamp [UCT]: 2024-08-04 17:03:38 Age [y:d:h:m:s]: 01:096:04:03:37
Block: 1080687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327218 RingCT/type: yes/0
Extra: 01d65d7df5086adc654c6a77d15f494a12e525d0a56fbcdbd5cfd7a514fb7fda0b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b0821dcb005c72a93bbbd16f0656faead5c660c8ffed88184780ca1b2e547dc 0.600000000000 1554140 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": 1080697, "vin": [ { "gen": { "height": 1080687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b0821dcb005c72a93bbbd16f0656faead5c660c8ffed88184780ca1b2e547dc" } } ], "extra": [ 1, 214, 93, 125, 245, 8, 106, 220, 101, 76, 106, 119, 209, 95, 73, 74, 18, 229, 37, 208, 165, 111, 188, 219, 213, 207, 215, 165, 20, 251, 127, 218, 11, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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