Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 085f71fc17832042f3691eb4711fb93684d14cadff99b16eb32b33c0b4d099f1

Tx prefix hash: bf0cbf44d7f9ea8deff37709d946fb4a8650dd9989194ec325ff93c88a0f230d
Tx public key: c671778c6eff5e4acb6caafce254ace7770cf9f5d67b2bea29b57ccb7d286d54
Timestamp: 1735954454 Timestamp [UCT]: 2025-01-04 01:34:14 Age [y:d:h:m:s]: 00:308:23:24:26
Block: 1189693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218325 RingCT/type: yes/0
Extra: 01c671778c6eff5e4acb6caafce254ace7770cf9f5d67b2bea29b57ccb7d286d54021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 972b21b726ca0f2355cbc1a591820fa218fe0520f8fcadee785c17380c78c48d 0.600000000000 1676204 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": 1189703, "vin": [ { "gen": { "height": 1189693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "972b21b726ca0f2355cbc1a591820fa218fe0520f8fcadee785c17380c78c48d" } } ], "extra": [ 1, 198, 113, 119, 140, 110, 255, 94, 74, 203, 108, 170, 252, 226, 84, 172, 231, 119, 12, 249, 245, 214, 123, 43, 234, 41, 181, 124, 203, 125, 40, 109, 84, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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