Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d440c7fb4c160a29bd19de417a4ef65bfaed118b3474ac62e679a60feeefdee

Tx prefix hash: 0f3abb7b4f7b8e71348a3b52d750c39d2e84a38afa291858f00662a86412ba32
Tx public key: 1e8bc151c01171d55051095c27b0c0552dc21f76034e1f906e4f8e34fd7f25d7
Timestamp: 1764662931 Timestamp [UCT]: 2025-12-02 08:08:51 Age [y:d:h:m:s]: 00:003:01:46:46
Block: 1424705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2212 RingCT/type: yes/0
Extra: 011e8bc151c01171d55051095c27b0c0552dc21f76034e1f906e4f8e34fd7f25d7021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05afee0bfc39909794854b9bd1f5e9050ff2683b65b419b7ded88385221e850c 0.600000000000 1913336 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": 1424715, "vin": [ { "gen": { "height": 1424705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05afee0bfc39909794854b9bd1f5e9050ff2683b65b419b7ded88385221e850c" } } ], "extra": [ 1, 30, 139, 193, 81, 192, 17, 113, 213, 80, 81, 9, 92, 39, 176, 192, 85, 45, 194, 31, 118, 3, 78, 31, 144, 110, 79, 142, 52, 253, 127, 37, 215, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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