Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0966f31adaa2cd2de875910cf7b3af08dbb64dfdb3a912ff6b012fe89dfeace1

Tx prefix hash: 973b5d45aee896d9c1a40b48d85fa865c48c958a3ea7e9986162d4e74efc2b22
Tx public key: c64342404c12efca4cc53425ba861d4fc96bfbdc3c4afa876ed1bd0ec92842de
Timestamp: 1737559409 Timestamp [UCT]: 2025-01-22 15:23:29 Age [y:d:h:m:s]: 00:147:08:19:20
Block: 1202934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105040 RingCT/type: yes/0
Extra: 01c64342404c12efca4cc53425ba861d4fc96bfbdc3c4afa876ed1bd0ec92842de021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfcc74f6f49d3610b5aa1568e136935c85cae58f9c7bb2e005e8c6f9608d3f15 0.600000000000 1689601 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": 1202944, "vin": [ { "gen": { "height": 1202934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfcc74f6f49d3610b5aa1568e136935c85cae58f9c7bb2e005e8c6f9608d3f15" } } ], "extra": [ 1, 198, 67, 66, 64, 76, 18, 239, 202, 76, 197, 52, 37, 186, 134, 29, 79, 201, 107, 251, 220, 60, 74, 250, 135, 110, 209, 189, 14, 201, 40, 66, 222, 2, 17, 0, 0, 0, 2, 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