Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe526afb13a9fa65c9bdddd39eb7d726a94f21fc7c1dc1af603a3393d127f440

Tx prefix hash: 4ad0291ef2efcf802c7dcae5ca2898ec1f9a915a817ebe4d5cee8a8ef30c836c
Tx public key: fd31e8aeeaabd0d729f27909f2d0762bbe0eb84be3d8340fe9797f22362c0d62
Timestamp: 1763819345 Timestamp [UCT]: 2025-11-22 13:49:05 Age [y:d:h:m:s]: 00:004:01:21:23
Block: 1417714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2902 RingCT/type: yes/0
Extra: 01fd31e8aeeaabd0d729f27909f2d0762bbe0eb84be3d8340fe9797f22362c0d620211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9053e30061dd1a80f954efe624fb739935c744804591e677ac2f6c7badb52d92 0.600000000000 1906239 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": 1417724, "vin": [ { "gen": { "height": 1417714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9053e30061dd1a80f954efe624fb739935c744804591e677ac2f6c7badb52d92" } } ], "extra": [ 1, 253, 49, 232, 174, 234, 171, 208, 215, 41, 242, 121, 9, 242, 208, 118, 43, 190, 14, 184, 75, 227, 216, 52, 15, 233, 121, 127, 34, 54, 44, 13, 98, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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