Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48aab3fb44996c67d77bed59abb9ce6cca4e05e9b171cc19fdd5cdffbd974100

Tx prefix hash: 6e4d0a6f519255c77178d842df5d0b2b64f08d23a8d5f099f8866e88796a41ac
Tx public key: d5294c15da623e8be87f3be4d5873f3ff5ea15567300f15d9bee8a7bf15e0775
Timestamp: 1707094278 Timestamp [UCT]: 2024-02-05 00:51:18 Age [y:d:h:m:s]: 01:133:05:00:52
Block: 950546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356206 RingCT/type: yes/0
Extra: 01d5294c15da623e8be87f3be4d5873f3ff5ea15567300f15d9bee8a7bf15e07750211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c7f0761b81308980012faa9f8f3c93e8750cbe54cb5c22a24cdf1b2f548aab0 0.600000000000 1409182 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": 950556, "vin": [ { "gen": { "height": 950546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c7f0761b81308980012faa9f8f3c93e8750cbe54cb5c22a24cdf1b2f548aab0" } } ], "extra": [ 1, 213, 41, 76, 21, 218, 98, 62, 139, 232, 127, 59, 228, 213, 135, 63, 63, 245, 234, 21, 86, 115, 0, 241, 93, 155, 238, 138, 123, 241, 94, 7, 117, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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