Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c31cf7be7b1ff04f495c90158f75a1a2769e91b593ac763707115c0ed5f09463

Tx prefix hash: fab5d3883c3ec7cab051af4bdad7fd5b987204ec5f0baa67fd402c8f33b4df37
Tx public key: 518d91963959bab6a690f4e1209e31ae80f631c9f77b87d65a4aec5c1243fca9
Timestamp: 1763360781 Timestamp [UCT]: 2025-11-17 06:26:21 Age [y:d:h:m:s]: 00:004:01:20:06
Block: 1413910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2890 RingCT/type: yes/0
Extra: 01518d91963959bab6a690f4e1209e31ae80f631c9f77b87d65a4aec5c1243fca9021100000001da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8ca0000204362d79e278635ecd07dfa80db1a44e3a4c917c6d50e890ff0fab6 0.600000000000 1902391 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": 1413920, "vin": [ { "gen": { "height": 1413910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8ca0000204362d79e278635ecd07dfa80db1a44e3a4c917c6d50e890ff0fab6" } } ], "extra": [ 1, 81, 141, 145, 150, 57, 89, 186, 182, 166, 144, 244, 225, 32, 158, 49, 174, 128, 246, 49, 201, 247, 123, 135, 214, 90, 74, 236, 92, 18, 67, 252, 169, 2, 17, 0, 0, 0, 1, 218, 85, 72, 72, 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