Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd613c8685623ae6e986cc0cf39890f69c0325f82d81e81c1f5e71ea0d716b14

Tx prefix hash: 19c7d5c63775ee9fa877a0072725b85118bafbec55b4dd2c69925f4a4a8ae6e3
Tx public key: f97d85b95fa13de83d30f28051627e5ec8bea08cdb006c77ec8f02c5a80e829d
Timestamp: 1763855301 Timestamp [UCT]: 2025-11-22 23:48:21 Age [y:d:h:m:s]: 00:030:23:01:11
Block: 1418008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22156 RingCT/type: yes/0
Extra: 01f97d85b95fa13de83d30f28051627e5ec8bea08cdb006c77ec8f02c5a80e829d02110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ddea9cdf871b91bcd74514d84179d4cee231c4089566e9fd8f8cb29809066bd 0.600000000000 1906535 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": 1418018, "vin": [ { "gen": { "height": 1418008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ddea9cdf871b91bcd74514d84179d4cee231c4089566e9fd8f8cb29809066bd" } } ], "extra": [ 1, 249, 125, 133, 185, 95, 161, 61, 232, 61, 48, 242, 128, 81, 98, 126, 94, 200, 190, 160, 140, 219, 0, 108, 119, 236, 143, 2, 197, 168, 14, 130, 157, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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